Oracle® Fusion Middleware

Error Messages

12c (12.1.2)

E40224-02

February 2014

Oracle Fusion Middleware Error Messages, 12c (12.1.2)

E40224-02

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

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

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

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

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

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

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

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

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

Contents

Preface

- Audience

- Documentation Accessibility

- Conventions

1 ADF_FACES-00001 to ADF_FACES-60098

2 ADF_TRINID-00001 to ADF_TRINID-30336

3 ADFC-00001 to ADFC-14018

4 ADFDI-00100 to ADFDI-55516

5 ADFF_BIND-00001 to ADFF_BIND-00046

6 ADFSHARE-00002 to ADFSHARE-00150

7 BEA-000001 to BEA-2163006

8 CLONE-20200 to CLONE-92302

9 CONF-30000 to CONF-35141

10 DVT-02012 to DVT-26021

11 HELP-00001 to HELP-40001

12 INST-01000 to INST-10117

13 J2EE HTTPC-00004 to J2EE HTTPC-12011

14 J2EE JMX-46000 to J2EE JMX-47006

15 J2EE JSP-00002 to J2EE JSP-00302

16 JBO-24000 to JBO-80008

17 JRF-10001 to JRF-20036

18 MDS-00001 to MDS-92006

19 MODPLSQL-00001 to MODPLSQL-00868

20 OAB-00015 to OAB-960018

21 ODI-01100 to ODI-999999

22 OHS-03501 to OHS-03813

23 SDP-25001 to SDP-26457

24 TPC-00001 to TPC-90022

25 TRS-10000 to TRS-30030

26 UCS-10106 to UCS-31204

27 UPGAST-00001 to UPGAST-00267

Preface

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

Audience

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

Documentation Accessibility

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

Access to Oracle Support

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

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

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

italic

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

monospace

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

1 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_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

3 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

4 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-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-05001: An unsupported binding type {0} exists in the page definition {1}.

Cause: An unsupported binding type was encountered in the page definition file.

Action: Remove the unsupported binding from the page definition file.
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-05010: unable to move the component to new position; cannot parse position {0}

Cause: The position specified for the new location of the component did not evaluate to a valid cell reference.

Action: Specify a valid cell reference. For example, use $B$3 for the cell in the second column and third row.
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 exceeds the length limitation imposed by Microsoft Excel.

Action: Reduce the length of the specified path and retry the publish operation.
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-05560: Download action ignored for insert-only table, {0}.

Cause: Download action has been included in an action-set, but is not applicable for an insert-only table.

Action: The developer should remove the action, or alter the table so it is no longer insert-only.
Level: 1

Type: WARNING

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-05590: A failure has occured while performing configuration tasks for the binding container: {0}.

Cause: The worksheet setup action failed with an exception.

Action: Review the server logs for more information on the root cause of this error.
Level: 1

Type: ERROR

Impact: Programmatic

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-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-07500: unable to find version converters to perform the metadata conversion.

Cause: Metadata converters for converting the workbook metadata to the current version cannot be found.

Action: Ensure there are converters supporting this conversion.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07501: unable to perform an XSL transformation to migrate metadata.

Cause: A failed attempt was made to perform an XSL transformation for migrating the metadata.

Action: Ensure both the XSLT stylesheet and the input XML document are correct.
Level: 1

Type: ERROR

Impact: Deployment

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-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-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

5 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

6 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

7 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: Using localhost as the ListenAddress when generating a Coherence WKA list will not operate correctly across multiple machines.

Cause: Server {0} is configured with 'localhost' as the ListenAddress. When using Coherence WKA and not explicitly defining a WKA list, the configuration may not operate correctly across multiple machines.

Action: Specify an appropriate hostname as the ListenAddress for this server.
Level: 1

Type: NOTIFICATION

Impact: weblogic-coherence-integration

BEA-000007: Could not find a referenced JNDI resource.

Cause: Could not find the JNDI resource [{0}] referenced by {1}.

Action: Define the JNDI resource [{0}] referenced by {1}.
Level: 1

Type: NOTIFICATION

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. 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.
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, 2011, 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}

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-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 the 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. Resources become unavailable to the application during the testing.

Action: Tune the MaxUnavailable attribute for the pool if so desired.
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, and 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 is 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 is being forcibly released back into 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 due to an internal client/server error that should be reported to My Oracle Support.
Level: 1

Type: ERROR

Impact: Common

BEA-000622: Ignoring an 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 shut down.

Action: Check application behavior. All resources should be closed before the application is shut down.
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 five 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 if the failure condition that prevents the resources from being created (for example, 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: The 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 the 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 they have obtained from the pool. It is possible that these resources may have been leaked by the applications.

Action: Check the 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-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-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. Starting service {1}, {2} of {3}. Last service {4} took {5} milliseconds.

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 configuration. The server 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 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-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-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-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-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-090570: {0} has been specified without enabling the SecurityManager.

Cause: The server has been told to boot with a JACC property enabled without also enabling a SecurityManager by setting the java.security.manager property. JACC depends on a SecurityManager being in place.

Action: If JACC is desired, then a SecurityManager must be enabled. This can be done by specifying a value for the java.security.manager property. If JACC is not desired then remove the specification of the JACC property.
Level: 1

Type: ERROR

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 quot;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-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 will be 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 purpose 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 encoding specified is not supported by the underlying virtual machine(VM).

Action: Ensure that the encoding specified 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 avaliable 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 the 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 the 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 startover 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 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. PEnsure 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 lookup 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). Such 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: More than one web fragments with the same name: "{0}".

Cause: More than one web fragments with the same name.

Action: Change one or more 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 found in web fragment.

Action: Make the Others element appeared in before or after only.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101382: WLServlet annotation can't be used with WebServlet together

Cause: WLServlet annotation can't be used with WebServlet together.

Action: Suggest to use servlet 3.0 annotations only
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-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-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 IO 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-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-149007: New source location, "{0}", cannot be deployed to the configured application, "{1}". The application source is at "{2}". Changing the source location is not allowed for a previously attempted deployment. Try deploying without specifying the source.

Cause: This error occurs when an attempt is made to change the source location for a previously configured application.

Action: Deploy the application with the same source location that was configured in the application.
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-149043: The staging mode cannot be changed for an application that has already been configured. The staging mode change has been rejected for application "{0}" from {1} to {2}.

Cause: An attempt was made to change the staging mode on an application.

Action: Try deploying without changing the staging mode.
Level: 1

Type: ERROR

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-149094: New version "{1}" of application "{0}" cannot be deployed to the source location, "{2}". The source location is the same as the nostage source location of a previously deployed application version "{3}".

Cause: This error occurs when an attempt is made to deploy a new application version with the same source location as the nostage source location of a previous application version.

Action: Deploy the new application version with a different source location. Also ensure that the old application source is still available at the old nostage source location.
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 {2} because application "{0}" is in state {1}

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: ERROR

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: JPA 2.0 API methods cannot be invoked on JPA 1.0 persistence provider. Update the application to use a JPA 2.0 compliant provider, such as EclipseLink, or ensure that the application does not attempt to invoke JPA 2.0 methods.

Cause: The application is invoking a method defined in JPA 2.0 but the persistence provider configured in the application is only JPA 1.0 compliant. Note the deprecated Kodo-OpenJPA persistence provider that ships with WebLogic Server does not support JPA 2.0.

Action: Update your application to use a JPA 2.0 compliant persistence provider, such as EclipseLink, or modify the application to ensure that only JPA 1.0 API methods are invoked.
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-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-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 since its ManagedConnectionFactory class has @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 define SharingScope explicitly. The pool does not support share by its design since its ManagedConnectionFactory class has @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-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: Informational message.

Action: No action 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: Informational message.

Action: No action 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 file 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 file store file.

Cause: See the detail message for the cause.

Action: Ensure that the hardware and operating system are functioning properly and that there is enough disk space available for the file store files.
Level: 1

Type: ERROR

Impact: Store

BEA-280020: There was an error while reading from the log file.

Cause: See the detail message for the cause.

Action: Ensure that the hardware and operating system are functioning properly and that all the persistent store files 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 persistent 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 persistent 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 persistent 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 file 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 persistent 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 file store: Code={0}.

Cause: The file store has been corrupted, possibly by a hardware or operating system error.

Action: 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 file store with an invalid version of {0}

Cause: The file 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 persistent 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 persistent 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 persistent 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 persistent 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 persistent 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 or the JDBC connection to the database.

Action: Restart the server.
Level: 1

Type: INTERNAL_ERROR

Impact: Store

BEA-280061: The persistent store "{0}" could not be deployed: {1}

Cause: See he detail message.

Action: See the detail message.
Level: 1

Type: ERROR

Impact: Store

BEA-280062: The persistent 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 linked exception (if one exists).

Action: See the exception text, and 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 linked exception text.

Action: See the exception text and 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 linked exception stack trace.

Action: See the linked exception text and 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 exception stack trace.

Action: See the text exception text and 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 persistent 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 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:

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:

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:

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-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:

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-280096: Opening existing file 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 store chapter of the Performance and Tuning 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: See the documentation for 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 "{1}" for the persistent store file "{0}" 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 admin compact utility to change block size, otherwise make sure that all store files 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 persistent 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 persistent 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: Unable to load the native wlfileio library for the persistent file store "{0}". The store will use buffered I/O. The store is still operating in a transactionally safe synchronous mode. See store open log messages for the requested and final write policies.

Cause: See message body.

Action: See the documentation for store synchronous write policy configuration.
Level: 1

Type: WARNING

Impact: Store

BEA-280110: The "{1}" attribute of Persistent 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 Persistent 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-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-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-300001: Could not execute command {0} for the Managed Server through the NodeManager, because the server name is not set.

Cause: No name has been specified for the Managed Server.

Action: Specify a name for the Managed Server in its configuration settings.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300002: Could not execute command {0} for the Managed Server {1} through the NodeManager because the domain name is not set.

Cause: No domain has been specified for the Managed Server.

Action: Verify that a domain has been specified for the Managed Server.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300004: Could not execute command {0} for the Managed Server {1} through the NodeManager because this command can only be performed from an admin server.

Cause: The WebLogic Server instance where the Administration Console is running is not an Administration Server.

Action: Run the WebLogic Administration Console on the Administration Server.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300005: Could not execute command {0} for server {1} through the NodeManager. This command {0} cannot be executed on the Administration Server using the NodeManager.

Cause: The NodeManager does not perform any operations on the Administration Server.

Action: No action is required as this operation is not supported on the Administration Server.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300006: Could not execute command {0} for server {1} using the NodeManager. Logs cannot be obtained for the Administration Server using the NodeManager.

Cause: The NodeManager does not perform any operations on the Administration Server.

Action: No action is required as this operation is not supported on the Administration Server.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300007: Could not execute command {0} for server {1} using the NodeManager, because the NodeManager does not monitor the Administration Server.

Cause: The NodeManager does not perform any operations on the Administration Server.

Action: No action is required as this operation is not supported on the Administration Server.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300009: Server {0} cannot be started in the standby state because the administration port is not configured.

Cause: An attempt was made to start a server in the standby state without configuring an administration port.

Action: Configure an administration port for the domain and retry the operation.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300010: Could not execute command {0} for server {1} using the NodeManager because the target machine configuration was not found.

Cause: No target machine has been associated with this server.

Action: Select a target machine to run this server on.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300011: Could not execute command {0} for server {1} using the NodeManager because the target machine configuration was not found. This feature is applicable only for servers that are started up through the NodeManager.

Cause: An attempt was made to use the NodeManager to perform an operation on a server that is only valid if the server was started using the NodeManager.

Action: Start the server using the NodeManager.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300012: Could not execute command {0} for server {1} using the NodeManager because the NodeManager configuration for target machine {2} was not found.

Cause: This is an internal error.

Action: Associate a machine on which server {1} is to be started by the NodeManager, then execute command {0}.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300013: Could not execute command {0} for server {1} using the NodeManager because the NodeManager configuration for target machine {2} was not found. This feature is applicable only for servers that were started up using the NodeManager.

Cause: An attempt was made to use the NodeManager to perform an operation on a server that is only valid if the server was started using the NodeManager.

Action: Configure the NodeManager for machine {3}, then execute command {0} for server {1}.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300014: Could not execute command {0} for server {1} using the NodeManager because the NodeManager listen address is not set.

Cause: The NodeManager address has not been set.

Action: Set a valid NodeManager listen address.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300015: Could not execute command {0} for server {1} using the NodeManager because the NodeManager listen port is not set.

Cause: The NodeManager port has not been set.

Action: Set a valid NodeManager listen port.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300016: Could not execute command {0} for server {1} using the NodeManager because the remote start configuration was not found.

Cause: The remote start configuration is missing.

Action: Set the remote start configuration for server {1} in the Remote Start tab on the configuration page for this server in the Administration Console.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300017: Could not execute command {0} for server {1} using the NodeManager because the username and password are not set.

Cause: The username and password to be used to boot the server are not set.

Action: Set the username and password in the Remote Start tab for the server in the Administration Console.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300018: Could not execute command {0} for server {1} using the NodeManager because the server listen address is not set.

Cause: The server listen address has not been set.

Action: Set a valid server listen address.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300019: Could not execute command {0} for server {1} using the NodeManager because the server listen port or protocol is not set.

Cause: The server listen port or protocol has not been set.

Action: Set a valid server listen port or protocol.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300020: Could not get logs for server {0} using the NodeManager because the specified log type {1} is invalid. This type can only be either WL_output or WL_error.

Cause: An attempt was made to get a log of an invalid type.

Action: Specify a valid type and retry the operation.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300021: Could not execute command {0} for server {1} using the NodeManager. Failed to create output file {2} in the directory {3}.

Cause: The specified log file could not be created.

Action: Verify that the disk is not full and retry the operation.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300022: Could not execute command {0} for server {1} using the NodeManager due to an internal error.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300026: The NodeManager command servlet was unable to send a reply to the NodeManager health query.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300027: The NodeManager command servlet received an invalid command.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300028: Error: Authentication Failure - {0}.

Cause: This is a security configuration error. The identity (username/password) specified in the Remote Start configuration of this server, which is used to boot the server, is being denied access to the server at runtime.

Action: Ensure that the identity specified in the Remote Start parameters for this server also has the privileges to access this server at runtime.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300029: Error: Action Failure - {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300030: The socket close failed. Reason: {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300032: Could not execute command {0} on the NodeManager. Unable to create file {1} under directory {2}.

Cause: The specified log file could not be created.

Action: Verify that the disk is not full and that the directory is writeable, then retry the operation.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300033: Could not execute command "{0}" on the NodeManager. Reason: "{1}".

Cause: The NodeManager command execution failed.

Action: No action is required.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300034: Could not execute command "{0}" for server "{1}" using the NodeManager. Reason: {2}.

Cause: Command execution for the server using the NodeManager failed.

Action: No action is required.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300035: Warning : {0}

Cause: Details of the cause are provided in the message.

Action: Details of the action are provided in the message.
Level: 1

Type: WARNING

Impact: NodeManager

BEA-300036: Error :{0}

Cause: Details of the cause are provided in the message.

Action: Details of the action are provided in the message.
Level: 1

Type: ERROR

Impact: NodeManager

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-300038: The NodeManager is unable to monitor this server. Could not create an SSL connection to the NodeManager. Reason : {0}

Cause: Check the message for details. This error might be due to a faulty SSL configuration.

Action: Check the message for details.
Level: 1

Type: WARNING

Impact: NodeManager

BEA-300039: The state change notification registration failed. The server will only be able to respond to the GETSTATE messages by the NodeManager. Reason : {0}

Cause: See the message for details.

Action: Check the message for details and take corrective action accordingly.
Level: 1

Type: ERROR

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-300041: Failed to register for startup mode change notification. Reason : {0}

Cause: Check the message for details.

Action: Check the message for details and take action accordingly.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300042: Failed to cancel the startup request to start the server {0} of domain {1}.

Cause: The server has advanced too far in the startup sequence.

Action: Shut down the server gracefully.
Level: 1

Type: WARNING

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. Also, 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-300045: An I/O error occurred while executing command "{0}" on the NodeManager.

Cause: The NodeManager command execution failed due to a file I/O or socket exception.

Action: Ensure that the NodeManager is running and listening on the configured address
Level: 1

Type: WARNING

Impact: NodeManager

BEA-300046: An I/O error occurred while executing command "{0}" for server "{1}" using the NodeManager.

Cause: The NodeManager command execution failed due to a file I/O or socket exception.

Action: Ensure that the NodeManager is running and listening on the configured address.
Level: 1

Type: WARNING

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. Also, 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. Also, 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-300051: An I/O error occurred while updating the startup properties for "{0}". This probably occured 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-300052: The specified script path, "{0}", contains improper characters. The script path must be a valid path that exists within the NodeManager script execution directory.

Cause: The specified script path, "{0}", contains improper characters.

Action: Ensure that the script path is a be a valid path that exists within the NodeManager script execution directory.
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 address specified 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 address specified and the server may not start without the available address. Configure an appropriate floating listen address for the server.

Action: Configure an appropriate floating listen address for the server.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-309999: {0}

Cause: Debugging - please do not change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

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/written: {0}.

Cause: The directory was not created the directory read/write permissions were not given to the directory.

Action: Create the destination directory with the appropriate read/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: 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: 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: Error occurred while sending a 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: Disk may be full or directory is not writable

Action: Check if disk is full or directory is unwritable
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320056: Log index file {0} has 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: Configured watch evaluated to true and 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: 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: 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-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-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-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 are more than one CoherenceClusterSystemResourceMBean defined using {0}

Cause: Multiple 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-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 maybe 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 application 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: Internal Error

Action: Contact Oracle Support for assistance.
Level: 1

Type: ERROR

Impact: Weblogic-Validation

BEA-2156402: Unable to process URL, {0}. Is from jar: {1} resourceDir: {2} resourcePath: {3}.

Cause: Internal Error

Action: Contact 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 determine the best way to fix it.
Level: 1

Type: ERROR

Impact: Weblogic-Validation

BEA-2156404: Unable to find a Validation Context. {0}

Cause: Internal Error

Action: Contact 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: Insure 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: WARNING

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-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

8 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-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: Provide the clone log and error file for investigation.
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 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 installer log and cloneAction log at following location {0} for more details.
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-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-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: Some files were missing from the Oracle Home {0}.

Action: Check the clone log file and permission restore log file {0} for more details about the missing files.
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.

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-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: Cloning is not possible.

Cause: The Oracle Home {0} was already registered with the Oracle Inventory.

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 an 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-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 characters, or the 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-20334: Invalid Domain home location.

Cause: Path "{0}" was not writable.

Action: Provide valid absolute writable path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20336: The move plan location is invalid.

Cause: There are three possible causes: 1. The path was not provided. 2. The move plan was not readable. 3. The path was not an absolute path.

Action: Provide a valid absolute path for the move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20337: Unable to persist the move plan.

Cause: Make sure that the move plan 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-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 move plan has more servers than in the source domain.

Action: Make sure that no new servers are added to the move plan.
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 move plan.
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 move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20347: Error in validating "DATASOURCE".

Cause: Specified move plan has more data sources than in the source domain.

Action: Make sure that no new data sources are added to the move plan.
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 move plan.
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 move plan.

Action: Make sure that valid values are provided in the move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20350: Error in validating "MACHINE_CONFIG".

Cause: Specified move plan has more machines than in the source domain.

Action: Make sure that no new machines are added to the move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20351: Error in validating "MACHINE_CONFIG".

Cause: Specified machine id {0} does not exist in the source move plan.

Action: Make sure that no new machines are added to the move plan 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 move plan.
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 move plan 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 move plan and the archive is valid.
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 move plan 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 move plans 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 move plan are not correct or some "READ_ONLY" properties in the move plans are modified or some internal error happened.

Action: Check the t2p logs for more details. Make sure that values in the move plans 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 move plan or the move plan is corrupted.

Action: Make sure that the move plan 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-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 move plan directory location.

Cause: Path {0} was either an empty string or not an absolute path.

Action: Provide an absolute path for the move plan 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 move plan had more clusters than in source domain.

Action: Make sure that no new clusters are added to the move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20388: Error in validating "CLUSTER_CONFIG".

Cause: Specified cluster {0} did not exist in source move plan.

Action: Make sure that no new clusters are added to the move plan 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 port {0} was not valid.

Action: Make sure that valid port numbers are specified in the move plan.
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 move plan.
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 sue 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-20402: The move plan 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 move plans and "READ_ONLY" properties are not changed.

Action: Check the t2p logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20406: Invalid move plan directory location.

Cause: Path {0} was either an empty string or not an absolute path.

Action: Provide an absolute path for the move plan directory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20407: Invalid move plan directory location.

Cause: Move plan directory location was empty.

Action: Provide an absolute path for the move plan 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 move plan 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 of "{1}" type.

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 directoy 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 either too short or too large.2. target Oracle home name had contained unsupported characters.

Action: Provide valid target Oracle home name.
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-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-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 Node Manager home.

Cause: Node Manager home location is empty.

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 is not empty.

Action: Provide valid location for Node Manager home. It should be empty or non-existing directory
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 move plan.
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 three 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.

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 move plan xml passed in the argument does not contain the same meta data as the one present in archiveMeta data property "{0}" from argument move plan is "{1}" Meta data property "{0}" from archive move plan is "{2}"

Action: Make sure the move plan 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 {0} passphrase file {1} 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.

Action: Make sure the Java used on target machine is from the same vendor and has the same major version. Example: 1.6 or 1.7
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 move plan.

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 move plan.

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 {0}

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-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 move plan 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-20937: "pasteConfig" operation of J2EE domain failed. Check 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 move plan 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-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-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-21123: Symbolic link file is not present or not properly linked, where absolute path should be "{0}" and canonical path should be "{1}", but canonical path found is "{2}".

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-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-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-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 move plan 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 move plan by merging move plan(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 move plan(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 move plan, 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 move plan from move plan {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 move plan.

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: Pasting Coherence Server configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21276: Pasting Coherence Cluster configuration.

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 move plan 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 occured 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-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 move plan. 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 (c) 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: Mutiple 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-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 move plans 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 sytem components {0} are configured in 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-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: Error in examining J2EE Domain. Check the logs for more details

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: Extract the packed domain from archive to temp location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23282: Reading the extracted domain template and pasting server, machine, cluster, datasource configuration changes...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23283: Unpack Domain.

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: Paste Server Configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23288: Paste Cluster Configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23289: Paste DataSource Configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23290: Paste Machine Configuration.

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 move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23294: Adding Adapter {0} to move plan.

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 move plan 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-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: Paste LDAP Authenticator Configuration

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-23319: Exporting metadata may take several minutes. Check the logs for monitoring the progress....

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: Paste RDBMS Security Store Configuration

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 move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23376: Adding application {0} deployment plan to the move plan.

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-23384: Stopping {0}...

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}.

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 move plan - {0} was not extracted using the archive - {1}. Please extract the move plan 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-27000: No ADF Connection MBeans were detected in the source domain, and therefore no ADF Connection information will be included in the moveplan.xml.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

CLONE-27010: One or more ADF Connection types for {0} are not supported and will not be included in the moveplan.xml.

Cause: One or more ADF Connection MBean does not provide the movableProperty annotation for at least one attribute.

Action: Validate that all ADF Connection MBean in your application have at least one property with movableProperty annotation with a value of "true".
Level: 1

Type: WARNING

Impact: Other

CLONE-27020: ADF Connection MBean {0}.{1} is read only. Changes for this ADF Connection will not be applied.

Cause: The ADF Connection MBean is read only.

Action: Validate that your application is configured with a writable Oracle MDS.
Level: 1

Type: WARNING

Impact: Other

CLONE-27100: Application {0} does not have ADF Connection MBean properties.

Cause: Application {0} does not have ADF Connection MBeans.

Action: Validate that the ADF web application module's web.xml was configured for ADF Connection MBeans or if the application does not have any ADF Connections.
Level: 1

Type: WARNING

Impact: Other

CLONE-27500: No Move Plan available.

Cause: Either ADF T2P plugin copy command failed, or the file is missing or corrupted.

Action: Validate that the Move Plan is valid after extraction from the copy command result.
Level: 1

Type: WARNING

Impact: Other

CLONE-28000: Unable to apply ADF Connection properties for Application "{0}"

Cause: This could be caused by an invalid Oracle MDS configuration in your application or a failure while attempting to apply attributes using JMX.

Action: Please validate that the application is configured with writable Oracle MDS.
Level: 1

Type: ERROR

Impact: Other

CLONE-28010: Start to run T2P ADF Connection Plugins.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-28020: Finish running T2P ADF Connection Plugins.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-28100: Starting WLS managed server {0}@{1}:{2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-28200: Stopping WLS managed server {0}@{1}:{2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-28300: Processing {0} ADF Connection MBean attributes at server {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-28400: No ADF Connectioin MBean with name {0}

Cause: OBJECT_NAME_PROPERTY field for mbean object name might be changed accidently.

Action: Use the value of OBJECT_NAME_PROPERTY from other attributes under the same ADF Connection MBean in Move Plan to correct the wrong one.
Level: 1

Type: WARNING

Impact: Other

CLONE-28500: Successfully saved ADF Connection MBean attributes update for application {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-28600: No ADF Connection MBean attributes changed for application {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-40001: OWSM Plug-in Copy Config Operation Started. Validating source environment.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40002: WSM-PM is not installed in domain. Repository data will not be moved.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40003: Reading bootstrap configuration file.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40004: Bootstrap configuration file modified on source environment. \"bootstrap.configmanager\" movable component will be added to move plan.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40005: Bootstrap configuration file \"wsm-config.xml\" is not modified on source environment.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40006: Reading WSM repository data.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40007: WSM repository data modified on source environment. \"wsm.repository\" movable component will be added to move plan.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40008: WSM repository data is not modified on source environment.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40009: OWSM plug-in movable component of type \"{0}\" will be added to move plan.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40010: WSM specific artifacts are not modified on source environment. Nothing will be added to move plan.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40011: OWSM Plug-in Copy Config operation finished.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40020: Unable to retrieve repository timestamp. Validation will not be performed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40021: OWSM Plug-in Paste Config operation started. Validating target environment.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40022: WSM-PM is not installed in target domain. Repository data will not be updated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40023: Updating repository data using move plan values. Extracting configuration groups from movable component.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40024: Repository movable component is not present in move plan. Repository data will not be updated

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40025: Updating bootstrap configuration using move plan values.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40026: Bootstrap movable component is not present in move plan. Bootstrap configurations will not be updated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40027: OWSM Plug-in Paste Config Operation Finished.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40028: Map file does not exist at {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40029: WSM repository archive file does not exist at {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40030: Error in importing repository data at target environment.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40031: Bootstrap file updated successfully, deleting original file.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40032: Error in updating bootstrap file, restoring original file.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40033: Repository timestamp updated successfully.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40034: Repository timestamp not updated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40035: OWSM Plug-in Paste Config Operation Finished.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40036: Domain name \"{0}\" will be changed to \"{1}\".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-40037: WSM Policy Manager is in active state.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42000: OWSM Plug-in source environment validation failed.

Cause: The method which checks if wsm-pm application is installed in domain failed.

Action: Make sure that admin server is up and wsm-pm applications is in active state, if installed.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42001: OWSM Plug-in copyConfig operation failed.

Cause: Execution of \"doCopyConfig\" failed.

Action: Check clone logs and server logs for more details.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42002: Error in generating map file for WSM Repository archive.

Cause: The map file for WSM repository archive could not be created.

Action: Check the clone logs and server logs for more details.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42003: OWSM plug-in target environment validation failed.

Cause: The method which checks if wsm-pm application is installed in domain failed.

Action: Make sure that admin server is up and wsm-pm applications is in active state, if installed.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42004: Error in reading wsm repository timestamp.

Cause: Either wsm-pm application is not active or connection credentials are incorrect.

Action: Make sure wsm-pm application is up and credentials are correct. Check clone logs and server logs for more details.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42005: Error in parsing move plan.

Cause: Specified move plan was not valid.

Action: Make sure that all the specified values in the move plan are correct.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42006: Error in extracting OWSM t2p directory.

Cause: Execution of \"extractWsmT2PFromRepository\" failed.

Action: Make sure that archive location is correct and is not corrupted. Check clone logs for details.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42007: WSM repository import failed.

Cause: WSM Repository data could not be imported.

Action: Make sure wsm-pm application is active. Check the clone logs and server logs for more details.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42008: Export WSM repository failed.

Cause: WSM Repository data could not be exported.

Action: Check the clone logs and server logs for more details.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42009: Error in adding file \"{0}\" to T2P archive.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42010: Error in reading bootstrap configuration file at source environment.

Cause: Either the file path is invalid or bootstrap file is of invalid format.

Action: Check the clone logs for more details.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42011: Error in reading bootstrap configuration file at target environment.

Cause: Either the file path is invalid or bootstrap file is of invalid format.

Action: Check the clone logs for more details.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42012: Error in reading map file generated by import repository command.

Cause: The location of the map file is invalid or map file does not exist.

Action: Check clone logs for more details.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42013: Error in reading map file generated by import repository command.

Cause: Generated map file is not of correct format.

Action: Check clone logs for more details.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42014: Error in retrieving the status of wsm-pm application.

Cause: The wsm-pm application is not up or the server on which wsm-pm is targeted is not up.

Action: Make sure server on which wsm-pm is targeted is not down and correct admin server credentials have been provided.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42015: Invalid map file location - {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42016: Invalid map file pattern - {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42017: Error in reading map file - {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42020: Invalid bootstrap configuration file location - {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42021: Error in updating bootstrap configuration file - {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42022: Unable to parse bootstrap configuration file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42023: Error in connecting to domain runtime.

Cause: Domain runtime connection to admin server could not be established.

Action: Make sure admin server is up and credentials are correct. Check clone logs for more details.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42024: Unable to retrieve information about listen (non-ssl) port.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42025: Unable to retrieve server bean object for admin server.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42026: Error is encountered in starting managed server.

Cause: The server where wsm-pm application is targeted could not be started.

Action: Check server logs and clone logs for more details.
Level: 1

Type: NOTIFICATION

Impact: Cloning

CLONE-42027: Error is encountered in stopping managed server.

Cause: The server where wsm-pm application is targeted could not be stopped.

Action: Check server logs and clone logs for more details.
Level: 1

Type: NOTIFICATION

Impact: Cloning

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

9 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

10 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

11 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

12 INST-01000 to INST-10117

INST-01000: Internal Error: Undefined module found: {0}.

Cause: The module {0} present in engineConfig.xml is undefined.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01001: Abnormal Program Termination.

Cause: The program has experienced an error for some internal or unexpected reason.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01002: Error: Undefined flag: {0}.

Cause: The flag {0} specified on the command line is not supported.

Action: Refer to the usage: setup.exe -help
Level: 1

Type: ERROR

Impact: Installation

INST-01003: Error: Response file not specified.

Cause: A response file must be provided when installing in the {0} mode.

Action: Specify a valid response file. Usage: setup.exe -s -response <Full path to response file>
Level: 1

Type: ERROR

Impact: Installation

INST-01004: Internal Error: File not found: {0}.

Cause: Page data definition {0} for page {1} not found.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01005: Internal Error: Multiple pages found with "{0}" attribute set to true.

Cause: There can be only one page with {0} attribute set to true.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01006: Internal Error: No page found with the "{0}" attribute set to true.

Cause: At least one page must have the "{0}" attribute set to true.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01007: Error: Invalid input: "{0}"

Cause: This error is caused due to invalid input on the command line

Action: Refer to the command line usage.
Level: 1

Type: ERROR

Impact: Installation

INST-01008: Internal Error: Operation not specified

Cause: Engine did not find an operation to run in this configuration.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01009: Error: Invalid flags specified for operation "{0}": "{1}"

Cause: Flags specified by the user on the command line are not supported for this operation:{0}

Action: Refer to the command line usage.
Level: 1

Type: ERROR

Impact: Installation

INST-01010: Internal Error: Parse error:{0}

Cause: A parse error occurred. The file:"{0}" is not in proper format.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01011: Internal Error: More than one incompatible operation specified: "{0}", "{1}"

Cause: Incompatible operation specified

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01012: Internal Error: More than one incompatible mode is specified at a time: "{0}", "{1}"

Cause: Incompatible modes specified

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01013: Internal Error: Default mode not specified for operation:{0}

Cause: Default mode not specified

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01014: Internal Error: Default Operation not specified.

Cause: Default Operation not specified

Action: Contact Oracle Support Services with these log files {0}{1}.
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01015: Internal Error: Found cyclic references to page: "{0}". Verify file: "{1}".

Cause: Cyclic references to other pages were found in the page data file: {0}

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01016: Internal Error: Multiple references of page: "{0}" found in the "{1}" section for page: "{2}"

Cause: Multiple next page references are not supported by the Oracle Install Engine.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01017: Internal Error: The following pages do not have a default next page specified: "{0}"

Cause: Default Next Page is mandatory for each page.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01018: Internal Error: Duplicate definition found for pages: "{0}".

Cause: Duplicate definition of pages detected.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01019: Internal Error: Next page sequence not specified for the following pages: "{0}".

Cause: In cases where multiple next pages follow this page, next page sequence is mandatory to define the page flow.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01020: Internal Error: Page definition not found for: "{0}".

Cause: Each Page should be accompanied by its page definition in the page data file.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01021: Internal Error: Page name not specified for file: "{0}".

Cause: Page name not specified

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01022: Internal Error: Page name mismatch. Names specified: "{0}" and "{1}".

Cause: Page name mismatch

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01023: Internal Error: Unable to provide usage

Cause: No usage available for this option: {0}. For more help refer this to Oracle Support Services.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01024: Invalid checkpoint file: {0}.

Cause: The existing checkpoint file is not in the correct format.

Action: Delete the invalid checkpoint file:{0}
Level: 1

Type: WARNING

Impact: Installation

INST-01025: Invalid checkpoint file: {0}. The release and/or version of the product in the checkpoint does not match the current product. {1}.

Cause: Not a valid checkpoint file for the current release/version.

Action: Delete the invalid checkpoint file
Level: 1

Type: WARNING

Impact: Installation

INST-01026: Response File parse error at Line no: {0} - {1}

Cause: The response file may be corrupted or has errors

Action: Correct the errors in the response file and try the install operation again.Check if you have missed specifying square brackets around the section names
Level: 1

Type: ERROR

Impact: Installation

INST-01027: Section name cannot be empty and should be enclosed in square brackets.

Cause: The Response File is not a valid response file. The Section Name is not specified or is not specified properly.

Action: The Response Files are organized into 4 sections namely ENGINE, GENERIC, SYSTEM AND APPLICATIONS. Each Section Should be enclosed in square brackets and appropriate entries should be specified under them (Example: [Generic]). Check the Section Names.
Level: 1

Type: ERROR

Impact: Installation

INST-01028: Error: No Section defined.

Cause: The Response File does not have any valid sections specified. The Response File is organized into 4 sections namely ENGINE, GENERIC, SYSTEM and APPLICATIONS.All Section Names are specified within square brackets.

Action: Verify the Specified Response Files for valid Section Names and Syntaxes
Level: 1

Type: ERROR

Impact: Installation

INST-01029: Response File Parse Error : No Equal Symbol "=" was found

Cause: The Format of specifying the value for a variable inside the response file is as VARIABLE_NAME=VALUE. The Equal Symbol "=" was missed

Action: Correct the Response File to specify the value for a variable as VARIABLE_NAME=VALUE. Insert the Equal Symbol "=" in appropriate position to correct the same
Level: 1

Type: ERROR

Impact: Installation

INST-01030: Response File Parse Error

Cause: The Variable {0} was not Found in the Response File

Action: Specify the Variable in the Response File. The Syntax of specifying a variable is as VARIABLE_NAME=VALUE
Level: 1

Type: ERROR

Impact: Installation

INST-01031: Response File Parse Warning. No value found. Ignoring.

Cause: The Variable {0} was found in the Response File with no value assigned to it and hence it was ignored while the Response File was Parsed.

Action: Specify the corresponding value.
Level: 1

Type: WARNING

Impact: Installation

INST-01032: Internal Error: Unable to create the Configuration Manager.

Cause: Configuration Files are not proper:{0}

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01033: Internal Error: Fatal Error Occurred while loading Configuration Actions.

Cause: Configuration Action Locations specified are incorrect:{0}

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01034: Internal Error: Fatal Error Occurred while publishing Configuration Actions.

Cause: Configuration Actions are improper:{0}

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01035: Internal Error: Fatal Error Occurred while loading Configuration Actions.

Cause: Configuration Actions are improper:{0}

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01036: Internal Error: Fatal Error Occurred while setting data for Configuration Actions.

Cause: Variable: {0} required by Action: {1} not found.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01037: Internal Error: Fatal Error Occurred while initializing data for Configuration Action.

Cause: Variable: {0} required by Action: {1} not initialized.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01038: Internal Error: Fatal Error Occurred while loading Configuration Action:{0}.

Cause: Class: {0} not found.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01039: Internal Error: Fatal Error Occurred while running lifecycle methods for Configuration Actions.

Cause: Lifecycle Error

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01040: Internal Error: There was an error while copying files to this location: {0}. Installation cannot continue.

Cause: Error in copying files

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01041: Response File Location:{0} is not readable.

Cause: Response File does not exist or does not have read permission. Response File path contains special characters.

Action: Ensure that the response file exists and is readable. The response file path must not contain any special characters.Only Alphanumeric, _, dot, and space characters are allowed.
Level: 1

Type: ERROR

Impact: Installation

INST-01042: An error occurred while reading the response file.

Cause: Response File does not exist at the specified location. Response file is not in the correct format.

Action: Ensure that the response file exists. Ensure that the Response File is in the correct format. The Response Files are organized into 4 sections namely ENGINE, GENERIC, SYSTEM AND APPLICATIONS.Each Section Should be enclosed in square brackets and appropriate entries should be specified under them.
Level: 1

Type: ERROR

Impact: Installation

INST-01043: Internal Error: Response File location not defined.

Cause: The file location provided to the writer is empty.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01044: Response File Location: {0} is not writable.

Cause: The specified file already exists or user does not have write permission in the given location. Response File path contains special characters.

Action: Ensure that the response file location is writable. The response file path must not contain any special characters.Only Alphanumeric,_,dot and space characters are allowed.
Level: 1

Type: ERROR

Impact: Installation

INST-01045: Response File Parse Error: Section Name "{0}" is invalid.

Cause: Section "{0}" does not exist.

Action: Ensure that the Section name is one of the following 1. ENGINE 2. GENERIC 3. SYSTEM 4. APPLICATIONS
Level: 1

Type: WARNING

Impact: Installation

INST-01046: Internal Error: Invalid Install Session.

Cause: Data Model is empty.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01047: Silent Install cannot continue, error {0}.

Cause: Data provided in the response file is insufficient to complete this installation. Data provided in the response file is incorrect and did not pass all the validations.

Action: Fill the indicated information in the response file and restart installation. Verify and change the indicated values specified in the response file and restart installation.
Level: 1

Type: ERROR

Impact: Installation

INST-01048: Internal Error: Aborting Silent Install.

Cause: Error while running silent install

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01049: There was a problem in creating the page sequence. Response File Data is incomplete.Error: {0}

Cause: Data provided in the response file is insufficient to complete this installation.

Action: Fill the indicated information in the response file and restart installation.
Level: 1

Type: ERROR

Impact: Installation

INST-01050: Some required prerequisites for this installation have failed. Installation cannot continue

Cause: Response File does not exist at the specified location. Response file is not in the correct format.

Action: Ensure that the response file exists. Ensure that the Response File is in the correct format. The Response Files are organized into 4 sections namely ENGINE, GENERIC, SYSTEM AND APPLICATIONS.Each Section Should be enclosed in square brackets and appropriate entries should be specified under them.
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01051: Some required prerequisites for this installation have failed. Installation cannot continue

Cause: Failed Prerequisite: {0}

Action: Take a look at the failed prerequisites and fix the necessary items. Restart the installation after you are done.
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01052: Error: Property: {0} does not belong to the Section: {1}. It will be ignored.

Cause: All variables in the response files are associated with a valid section. The variable specified in the response file does not belong to the section it appears in.

Action: Check if the variable is actually a valid property name and is present in the appropriate section.
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01053: [CONFIG]:: ACTION: {0} running.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01054: [CONFIG]:: STEP {0} running.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01055: Configuration Directory:{0} does not exist.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Installation

INST-01056: The file:{0} cannot be loaded as a configuration action.

Cause: The Configuration framework loads the configuration actions from jars or xml files. This file does not represent a configuration action.

Action: Correct the file and retry
Level: 1

Type: WARNING

Impact: Installation

INST-01057: Invalid Log level: {0} specified.

Cause: Log levels that can be specified on the command line can be: INFO, ERROR, DEBUG

Action: Specify a valid log level.
Level: 1

Type: WARNING

Impact: Installation

INST-01058: Log level changed to: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01059: Following checks will be retried by the Prerequisites checker:{0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01060: Error: Prerequisite check: {0} has failed.

Cause: Prerequisite check: {0} has failed

Action: Correct the failed prerequisite and retry
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01061: Warning: An optional Prerequisite check: {0} has failed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01062: Invalid Inventory Pointer location: {0} specified on the command line.

Cause: Inventory pointer file does not exist. Directory specified for the inventory cannot be created.

Action: Create a valid inventory pointer file at the location which is specified on the command line. Inventory pointer file is a property file containing two entriesinventory_loc=<Directory where new inventory is present or to be created>GROUP=<group of the installing user>
Level: 1

Type: ERROR

Impact: Installation

INST-01063: Invalid inventory location:{0}.

Cause: Directory specified for the inventory cannot be created.

Action: Provide a writable directory for the inventory.
Level: 1

Type: ERROR

Impact: Installation

INST-01064: Oracle home value was not set by the Installer.

Cause: Required Oracle home value not set

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01065: Library: {0} required for Action: {1} not found.

Cause: Required library not found

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01066: Configuration Data Store not found.

Cause: Required Configuration Data Store not found

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01067: Error while loading Configuration Actions from file: {0}

Cause: Problem while loading the configuration actions

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01068: No configurations defined for this installation.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01069: Internal Error: Unable to load Configuration Action: {0}

Cause: Class not found: {0}

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01070: Internal Error: Entry Point for Configuration Not Found.

Cause: Entry point not found

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03000: Error: ClassName is blank in roadmap file for page: {0}

Cause: The ClassName provided for the page named {0} is either null or blank or the class is nonexistent.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: ERROR

Impact: Installation

INST-03001: Error: ClassName is null or not provided in roadmap file for page: {0}

Cause: The ClassName provided for the page named {0} is either null or blank or the class is nonexistent.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: ERROR

Impact: Installation

INST-03002: Error: Class {0} is not found.

Cause: Either Class {0} is not present or it has an invalid format or it has been compiled with a different version of java compiler.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: ERROR

Impact: Installation

INST-03003: Internal Error: Runtime error occurred while loading page : {0}

Cause: Error occurred while loading the class for page {0}

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03004: Internal Error: The Resource Key name provided is blank

Cause: Resource Key name provided is blank

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03005: Internal Error: Exception occurred while constructing the Navigation Tree

Cause: Error while constructing the Navigation Tree

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03006: Internal Error: Exception occurred while preparing the Action Queue

Cause: Error occurred while preparing the Action Queue

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03007: Internal Error: Exception occurred while loading the help files.

Cause: The help files are corrupt or the help files are not present.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03008: Internal Error: Exception occurred while parsing the displayConfig.xml file

Cause: The format of displayConfig.xml is corrupt.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03009: Internal Error: Exception occurred launching the welcome window.

Cause: Error occurred launching the welcome window

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03010: Internal Error: Exception occurred launching the Wizard.

Cause: Error occurred launching the Wizard

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03011: Internal Error: Exception occurred while setting the UI default properties.

Cause: Error occurred while setting the UI default properties

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03012: Internal Error: Unknown Exception occurred.

Cause: Unknown exception occurred during installation

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03013: Internal Error: Exception while creating the Wizard Sequence

Cause: The sequence provided in roadmap.xml is not proper.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03014: Internal Error: Exception occurred while creating the validation tree

Cause: Error occurred while creating the validation tree

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03015: Internal Error: Exception occurred while selecting the next page.

Cause: Error occurred while selecting the next page

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03016: Internal Error: Exception occurred while updating the data model with user-specified data

Cause: Error occurred while updating the data model with user-specified data

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03017: Internal Error: Exception occurred while restoring the data from checkpoint.

Cause: The checkpoint data is corrupted.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03018: Internal Error: Exception occurred while shrinking the image.

Cause: Either the image is corrupted or the machine has not enough memory to perform the operation.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03019: Internal Error: Error while fetching the image.

Cause: Either the image is not present or the image is corrupted.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03020: Error in connecting to the Database. Connect string is missing

Cause: Connect String is missing

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-03021: Error in connecting to the Database

Cause: Unable to connect to the Database with the given credentials

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-03022: Error in validating Database details. Schema Type is missing

Cause: Schema Type is missing

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-03023: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Listener could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-03024: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid user name/password

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-03025: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. User is not a SYSDBA

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-03026: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Database could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-03027: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service id

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-03028: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service name

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-03029: Error in validating Database details

Cause: Could not find {0} type Schema in the Database

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-05100: Error in obtaining default DN Value

Cause: Error in processing the handler

Action: No default DN provided
Level: 1

Type: ERROR

Impact: Installation

INST-05115: Error in selection of component configuration.

Cause: At least one component needs to be selected for configuration

Action: Select at least one of Oracle Directory Integration Platform, Oracle Internet Directory, Oracle Virtual Directory or Oracle Directory Service Manager component to configure.
Level: 1

Type: ERROR

Impact: Installation

INST-05116: Error in obtaining Schema names.

Cause: One or more of the Database Connection parameters is missing.

Action: Enter all the fields in the screen.
Level: 1

Type: ERROR

Impact: Installation

INST-05117: Error in obtaining Schema names.

Cause: The format of Database Host field value is improper.

Action: Enter Database Host field in proper format.
Level: 1

Type: ERROR

Impact: Installation

INST-05118: The specified username does not have Database Administrator privileges.

Cause: Username {0} does not have Database Administrator privileges.

Action: Enter the username with Database Administrator privileges.
Level: 1

Type: ERROR

Impact: Installation

INST-05119: Error in retrieving schema details for component {0}.

Cause: The Schema for corresponding component is not loaded in the Database

Action: Make sure that the Database is loaded with the schema {0} or unselect the component {1} from Applications To Configure Screen.
Level: 1

Type: ERROR

Impact: Installation

INST-05120: Error in retrieving schema version.

Cause: Schema version for component {0} is missing.

Action: Check the values. Make sure the Database is loaded with required schemas.
Level: 1

Type: ERROR

Impact: Installation

INST-05121: An unsupported schema is detected.

Cause: The Schema Version for component {0} is less than 10.1.2.0.0

Action: This is an unsupported schema version. Upload the newer schema to continue installation.
Level: 1

Type: ERROR

Impact: Installation

INST-05122: Upgrade Scenario Detected

Cause: The Schema Version for component Oracle Internet Directory is {0}.

Action: The database you selected is associated with a previous version of Oracle Application Server. After the installation is complete, you must run the Oracle Fusion Middleware Upgrade Assistant. Choose YES to continue or NO to go back to the same screen and specify different database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05123: Error while retrieving the schema Name.

Cause: The Schema Name for component {0} is missing.

Action: Enter valid Database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05124: Error in connecting to the Database.

Cause: Could not connect to the Database with the given credentials

Action: Check the values. Make sure the Database is up and running and connect string, username and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05125: Error in retrieving schema details.

Cause: Database schemas were not found in the Database

Action: Run Oracle Metadata Repository Creation Utility and load the schemas.
Level: 1

Type: ERROR

Impact: Installation

INST-05126: Error in connecting to the LDAP.

Cause: One or more of LDAP Connection parameters is missing

Action: Enter all the fields in the screen.
Level: 1

Type: ERROR

Impact: Installation

INST-05127: Error in connecting to the LDAP.

Cause: Could not connect to the LDAP with the given credentials on SSL port

Action: Check the values of LDAP Connect parameters. Make sure LDAP HostName and SSL Port are in proper format.
Level: 1

Type: ERROR

Impact: Installation

INST-05128: Error while retrieving {0} password from LDAP.

Cause: The {0} password retrieved from LDAP is empty

Action: Check the values. Make sure the LDAP details are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05129: Error in connecting to the LDAP.

Cause: Could not connect to the LDAP with the given credentials on SSL port.

Action: Check the values. Make sure the LDAP is up and running on SSL port and LDAP Connect String, username and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05131: Error in component selection for Oracle Identity Management installation.

Cause: No components selected for Oracle Identity Management installation.

Action: Select at least one component for installation.
Level: 1

Type: ERROR

Impact: Installation

INST-05135: Error in retrieving default JPS attributes from LDAP.

Cause: The LDAP hostname is missing.

Action: Specify a valid Oracle Database eligible for OID upgrade.
Level: 1

Type: ERROR

Impact: Installation

INST-05136: Error in retrieving default JPS attributes from LDAP.

Cause: The LDAP port number is missing.

Action: Specify a valid Oracle Database eligible for OID upgrade.
Level: 1

Type: ERROR

Impact: Installation

INST-05137: Error in retrieving Oracle Internet Directory Details from the database

Cause: The Oracle Internet Directory Details in the database are not available.

Action: Check the repository mentioned for Oracle Single Sign On upgrade.
Level: 1

Type: ERROR

Impact: Installation

INST-05138: Error in retrieving Oracle Internet Directory Details from the database

Cause: Exception thrown while retrieving Oracle Internet Directory Details from the repository

Action: Check the repository mentioned for Oracle Single Sign On upgrade.
Level: 1

Type: ERROR

Impact: Installation

INST-05139: Upgrade Scenario Detected

Cause: The Schema Version for component Oracle Single Sign On is {0}

Action: The database you selected is associated with a previous version of Oracle Application Server. After the installation is complete, you must run the Oracle Fusion Middleware Upgrade Assistant. Choose YES to continue or NO to go back to the same screen and specify different database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05141: Missing Schema Detected

Cause: The {0} component schema is not loaded.

Action: One or more component schemas are not loaded in the specified database. Choose YES to continue or NO to go back to the same screen and specify different database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05142: Missing Schema Detected

Cause: The {0} component schema is not loaded.

Action: One or more component schemas are not loaded in the specified database. Choose YES to continue or NO to go back to the same screen and specify different database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05145: Error in checking for second OID installation against same database.

Cause: Exception thrown during second OID installation check.

Action: Choose valid ODS schema in the screen. Make sure that OID is up and running.
Level: 1

Type: ERROR

Impact: Installation

INST-05146: ODS Schema in use

Cause: ODS Schema is in use.

Action: The ODS schema chosen is already being used by an existing OID. Hence, the new OID being configured would reuse the same schema. Choose YES to continue or NO to choose a different ODS schema.
Level: 1

Type: ERROR

Impact: Installation

INST-05147: Missing Schemas Detected

Cause: The {0} component schemas are not loaded.

Action: One or more component schemas are not loaded in the specified database. Choose YES to continue or NO to go back to the same screen and specify different database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05149: Error in selection of component configuration.

Cause: Selecting DIP only is not allowed for create domain scenario.

Action: Select OID also whenever DIP is selected.
Level: 1

Type: ERROR

Impact: Installation

INST-05150: Error in selection of component configuration.

Cause: None of the components are selected for configuration.

Action: Select at least one component for configuration.
Level: 1

Type: ERROR

Impact: Installation

INST-05151: Error in retrieving default JPS attributes from LDAP.

Cause: One or more of LDAP Connection parameters is missing

Action: Check the values. Make sure the LDAP details are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05152: Error in validating LDAP Attributes.

Cause: Error in validating LDAP Attributes.

Action: Check the values. Make sure the LDAP details are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05155: Error in JPS Attributes validation.

Cause: The value entered in the {0} field is incorrect.

Action: Check the value. Make sure the value is present in LDAP.
Level: 1

Type: ERROR

Impact: Installation

INST-05156: Error in connecting to LDAP.

Cause: Could not connect to the LDAP with the given credentials.

Action: Check the values. Make sure the LDAP is up and running.
Level: 1

Type: ERROR

Impact: Installation

INST-05159: Partial Schema Detected.

Cause: Partial Schema Detected.

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-05162: Error in connecting to LDAP.

Cause: The value entered for OID Administrator Password is incorrect.

Action: Check the value. Make sure you have entered a valid value for OID Administrator Password.
Level: 1

Type: ERROR

Impact: Installation

INST-05163: Error in connecting to LDAP.

Cause: Error in connecting to LDAP.

Action: The LDAP is not up and running. Choose YES to continue or NO to choose a different ODS schema.
Level: 1

Type: ERROR

Impact: Installation

INST-05164: {0} is missing.

Cause: {0} is missing.

Action: Enter valid value for {0}.
Level: 1

Type: ERROR

Impact: Installation

INST-05165: {0} is not valid.

Cause: Error in validating {0}.

Action: Enter valid value for {0}.
Level: 1

Type: ERROR

Impact: Installation

INST-05166: An unsupported database version is detected.

Cause: The Database version {0} is not supported.

Action: Enter Database with version equal to or higher than 10.2.0.4.0 in 10g or version equal to higher than 11.1.0.6.0 in 11g.
Level: 1

Type: ERROR

Impact: Installation

INST-05167: Database Initialization Parameter Warning

Cause: The Database initialization parameter 'processes' has a value less than 500.

Action: Recommended value for Database initialization parameter 'processes' is 500. Choose YES to continue or NO to go back to the same screen and specify different database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05168: Prereqs Error

Cause: Prerequisites requirement check failed. The value of session_cached_cursors is less than 100.

Action: Required value of session_cached_cursors is 100. Specify another Database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05169: Validation of Host name failed. Invalid Host

Cause: The host name entered is not valid

Action: Provide a valid host name in format host:port
Level: 1

Type: ERROR

Impact: Installation

INST-05170: Validation of Host URL failed. Invalid Host URL

Cause: The host URL entered is not valid

Action: Provide a valid host URL in format ldap://host:port or ldaps://host:port
Level: 1

Type: ERROR

Impact: Installation

INST-05171: Error in validating LDAP Credentials

Cause: Specified LDAP Type ( {0} ) is not valid

Action: Valid values are "{0}". Enter a valid LDAP Type
Level: 1

Type: ERROR

Impact: Installation

INST-05172: Cannot connect. Specified schema account is locked

Cause: Specified {0} schema account is locked

Action: Unlock the {0} schema account.
Level: 1

Type: ERROR

Impact: Installation

INST-05173: Multilingual Support Warning

Cause: Multilingual Support Warning

Action: The database you are connecting is with non-AL32UTF8 character set. Oracle strongly recommends using AL32UTF8 as the database character set. Choose YES to continue or NO to go back to the same screen and specify different database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05174: Schemas existing in Database

Cause: Required schemas are already loaded in the specified database.

Action: Specify another database details or select the Use Existing Schema option.
Level: 1

Type: ERROR

Impact: Installation

INST-05175: Validation of LDAP Type failed. Invalid LDAP Type

Cause: The LDAP type entered is not valid

Action: Provide a valid LDAP type.
Level: 1

Type: ERROR

Impact: Installation

INST-05176: Validation of Host URL failed. Invalid Host URL

Cause: The host URL entered is not valid.

Action: Provide a valid SSL LDAP connection URL of the format ldaps://host:port
Level: 1

Type: ERROR

Impact: Installation

INST-05177: Invalid Oracle Identity Federation schema

Cause: The username entered is not a valid Oracle Identity Federation schema.

Action: Provide a valid Oracle Identity Federation schema name.
Level: 1

Type: ERROR

Impact: Installation

INST-05178: Error in connecting to LDAP.

Cause: Could not connect to the LDAP in SSL mode with the given credentials.

Action: Check the values. Make sure the LDAP is up and running. Provide valid SSL LDAP connection details.
Level: 1

Type: ERROR

Impact: Installation

INST-05179: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service id

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05180: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service name

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05181: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials for {0}. Listener could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password for {0} are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05182: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid user name/password

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05183: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. User is not a SYSDBA

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05184: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Database could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05185: Error in validating login table

Cause: The Login Table is not valid.

Action: Enter valid Login Table name.
Level: 1

Type: ERROR

Impact: Installation

INST-05186: Error in validating user id attribute

Cause: The User ID Attribute is not valid.

Action: Enter valid User ID Attribute value.
Level: 1

Type: ERROR

Impact: Installation

INST-05187: Error in validating user id attribute

Cause: The User Description Attribute is not valid.

Action: Enter valid User Description Attribute value.
Level: 1

Type: ERROR

Impact: Installation

INST-05188: Error in validating Oracle Identity Federation User Store RDBMS Attributes

Cause: The Oracle Identity Federation User Store RDBMS Attributes are not valid.

Action: Enter valid values for Login Table, User ID Attribute and User Description Attribute.
Level: 1

Type: ERROR

Impact: Installation

INST-05189: An unsupported database version is detected.

Cause: The Database version {0} is not supported for upgrade scenario.

Action: Enter Database with version equal to or higher than 10.2.0.3.0 or 11.1.0.6.0.
Level: 1

Type: ERROR

Impact: Installation

INST-05190: Unable to connect to Oracle WebLogic Middleware Administration Server. Host name is missing.

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server. Host name is missing.

Action: Enter a valid host name
Level: 1

Type: ERROR

Impact: Installation

INST-05191: Error in obtaining connection with Oracle WebLogic Middleware Administration Server

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server. Credentials entered are empty or contain invalid characters

Action: Make sure the Middleware Administration Server is up and host name, port, user name and administration password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-05192: Unable to connect to Oracle WebLogic Middleware Administration Server. Port number is missing.

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server. Port number is missing.

Action: Enter a valid port
Level: 1

Type: ERROR

Impact: Installation

INST-05193: Unable to connect Oracle WebLogic Middleware Administration Server. Admin User name is missing.

Cause: Unable to connect Oracle WebLogic Middleware Administration Server. Admin User name is missing.

Action: Enter a valid admin user name
Level: 1

Type: ERROR

Impact: Installation

INST-05194: Error in obtaining connection with Oracle WebLogic Middleware Administration Server

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server.

Action: Make sure the Oracle Middleware Administration Server is up and host name, port, user name and administration password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-05195: Error in installing DIP/ODSM in two different machines.

Cause: Unable to install DIP/ODSM in two different machines.

Action: Make sure DIP and ODSM are configured on the same machine.
Level: 1

Type: ERROR

Impact: Installation

INST-05196: Error in getting the IP address for the localhost.

Cause: Unable to get the IP Address for the localhost.

Action: Make sure that the security manager existing on the system allows access to the IP Address.
Level: 1

Type: ERROR

Impact: Installation

INST-05197: Error in validating LDAP Attributes.

Cause: Error in validating Domain Name.

Action: Check the values. Make sure the Domain Name is correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05198: Specified Oracle Identity Federation schema is not empty.

Cause: Error in validating Oracle Identity Federation schema.

Action: Check the values. Make sure the Oracle Identity Federation schema is not loaded with Oracle Identity Federation configuration data.
Level: 1

Type: ERROR

Impact: Installation

INST-05199: Error in validating {0}.

Cause: Unable to validate the field {0}.

Action: Check the values. Make sure the value for {0} is correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05200: Error in validating {0} home location

Cause: Enter a valid value for {0} home location

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-05201: Error in validating {0} home location

Cause: Specified {0} home location does not exist

Action: Provide an exisiting {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-05202: Error in validating {0} home location

Cause: Specified {0} home location does not have read/write permissions

Action: Provide read/write permissions for the {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-05203: Error in validating {0} home location

Cause: Specified {0} home location is either not valid or empty

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-05204: Error in validating {0} home location

Cause: Specified {0} home location is not a valid location

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-05205: Error in validating {0} home location

Cause: An unexpected error occurred during the validation of {0} home location

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-05206: Error in validating Database block size.

Cause: The Database block size is less than 8KB.

Action: Make sure that the Database block size is greater than 8KB.
Level: 1

Type: ERROR

Impact: Installation

INST-05207: Error in connecting to OID.

Cause: Unable to connect to OID with the given credentials.

Action: Make sure that the OID is up and running.
Level: 1

Type: ERROR

Impact: Installation

INST-05208: Missing Schema Detected

Cause: The {0} component schema is not loaded.

Action: One or more component schemas are not loaded in the specified database.
Level: 1

Type: ERROR

Impact: Installation

INST-05209: Unable to configure DIP and ODSM in two different machines.

Cause: Installer has detected that DIP is already configured on a different machine in the domain, unable to configure ODSM on this machine.

Action: Make sure that DIP and ODSM are configured on the same machine.
Level: 1

Type: ERROR

Impact: Installation

INST-05210: Unable to configure DIP and ODSM in two different machines.

Cause: Installer has detected that ODSM is already configured on a different machine in the domain, unable to configure DIP on this machine.

Action: Make sure that DIP and ODSM are configured on the same machine.
Level: 1

Type: ERROR

Impact: Installation

INST-05211: Error in selection of component configuration.

Cause: The values entered for the components to configure are either not valid or empty.

Action: Provide valid values for the components to configure.
Level: 1

Type: ERROR

Impact: Installation

INST-05212: Error in selection of component configuration.

Cause: Select DIP or ODSM or OIF for configuration in expand cluster flow.

Action: Make sure that at least one cluster is selected for configuration.
Level: 1

Type: ERROR

Impact: Installation

INST-05213: Warning

Cause: The Database version {0} is not supported.

Action: Enter Database with version equal to or higher than 10.2.0.4.0 in 10g or version equal to higher than 11.1.0.7.0 in 11g. Refer to the certification matrix for supported database versions.
Level: 1

Type: ERROR

Impact: Installation

INST-05214: Error in providing cluster connection information.

Cause: The values entered to connect the cluster are either not valid or empty.

Action: Provide valid values to connect the cluster.
Level: 1

Type: ERROR

Impact: Installation

INST-05215: Error in finding cluster.

Cause: Could not find a cluster of Identity Management Components in the domain.

Action: Make sure to configure at least one cluster in the domain.
Level: 1

Type: ERROR

Impact: Installation

INST-05216: Error in obtaining connection with Oracle WebLogic Middleware Administration Server

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server.

Action: Make sure the Oracle Middleware Administration Server is up and hostname, port, user name and administration password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-05217: Error in detecting machine platform or JVM bits.

Cause: Unable to detect machine platform or JVM bits.

Action: Make sure machine platform and JVM are supported.
Level: 1

Type: ERROR

Impact: Installation

INST-05218: Cannot install or configure IDM on a 32-bit JVM on a 64-bit machine.

Cause: Unable to install or configure IDM on a 32-bit JVM on a 64-bit machine.

Action: Make sure to install and configure IDM in supported modes.
Level: 1

Type: ERROR

Impact: Installation

INST-05219: Error in providing OID with compatible version.

Cause: OID version is incompatible.

Action: Provide OID with compatible version.
Level: 1

Type: ERROR

Impact: Installation

INST-05223: Error in validating Domain.

Cause: Specified domain is not a valid IDM Domain.

Action: Provide valid IDM domain details.
Level: 1

Type: ERROR

Impact: Installation

INST-07000: Error in validating {0} location

Cause: {0} location specified is null or contains invalid characters

Action: The directory name may only contain alphanumeric, underscore (_), hyphen (-) , or dot (.) characters, and it must begin with an alphanumeric character. Provide a different directory name.
Level: 1

Type: ERROR

Impact: Installation

INST-07001: Validation of {0} location failed. Null Value

Cause: Provide a valid value for {0} location.

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07002: Validation of {0} location failed. String is too long.

Cause: Specified {0} location: {1} is too long

Action: Change the path to a value that is less than or equal to {2} characters
Level: 1

Type: ERROR

Impact: Installation

INST-07003: Validation of {0} location failed. Not Absolute.

Cause: {0} location is not absolute path

Action: Provide an absolute path
Level: 1

Type: ERROR

Impact: Installation

INST-07004: Validation of {0} location failed. Invalid Characters.

Cause: {0} location contains one or more invalid characters

Action: The directory name may only contain alphanumeric, underscore (_), hyphen (-) , or dot (.) characters, and it must begin with an alphanumeric character. Provide a different directory name.
Level: 1

Type: ERROR

Impact: Installation

INST-07005: Validation of {0} location failed. Directory already Exists.

Cause: Validation of {0} location failed. The location specified already exists and is a nonempty directory

Action: Provide an empty or nonexistent directory location
Level: 1

Type: ERROR

Impact: Installation

INST-07006: Validation of {0} location failed. No read/write permission.

Cause: Validation of {0} location failed. The location specified does not have read/write permissions

Action: Provide a location with read/write permission
Level: 1

Type: ERROR

Impact: Installation

INST-07007: Validation of {0} location failed. Directory exists as a file.

Cause: Validation of {0} location failed. The location specified already exists and is a file

Action: Provide an empty or nonexistent directory location
Level: 1

Type: ERROR

Impact: Installation

INST-07008: Validation of {0} location failed. No create permission.

Cause: Validation of {0} location failed. User does not have permission to create home/instance location

Action: Make sure that you have the required permission to create the directory
Level: 1

Type: ERROR

Impact: Installation

INST-07009: Error in validating {0} location

Cause: An unexpected error occurred while validating {0} location

Action: Enter a valid directory
Level: 1

Type: ERROR

Impact: Installation

INST-07010: Error in validating the Front End URL

Cause: Front End URL value is null or contains invalid characters

Action: Provide a valid URL in [http://host.domainname:port] format
Level: 1

Type: ERROR

Impact: Installation

INST-07011: Validation of Front End URL failed. Null Value

Cause: Provide a valid value for Front End URL

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07012: Validation of Front End URL failed. Invalid Protocol

Cause: Validation of Front End URL failed. The protocol entered is not valid

Action: Provide a valid protocol. The valid protocol list is {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07013: Validation of Hostname failed. Invalid Host

Cause: The hostname entered is not valid

Action: Provide a valid hostname
Level: 1

Type: ERROR

Impact: Installation

INST-07014: Validation of port value failed. Invalid port

Cause: The port entered is not valid

Action: Provide a valid port number
Level: 1

Type: ERROR

Impact: Installation

INST-07015: Validation of Front End URL failed. Invalid format

Cause: Validation of Front End URL failed. The front end URL entered is not valid

Action: Provide a valid URL in [http://host.domainname:port] format
Level: 1

Type: ERROR

Impact: Installation

INST-07016: Error in validating the Front End URL

Cause: An unexpected error occurred while validating the Front End URL

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07017: Error in obtaining free space

Cause: Error in obtaining free space. Value for drive name contains invalid characters

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07018: Error in obtaining free space. Null Value

Cause: Error in obtaining free space. Value for drive name is null

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07019: Error in obtaining free space

Cause: An unexpected error occurred while calculating available free space

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07020: Error in obtaining default {0} location

Cause: An unexpected error occurred while obtaining default home location

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07021: Error in obtaining available Oracle homes

Cause: An unexpected error occurred while obtaining available Oracle homes

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07033: Error in validating the {0} field value

Cause: {0} field value is null or contains invalid characters.

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07034: Error in validating the {0} field value

Cause: Provide a value for {0}

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07035: Error in validating the {0} field value. Length less than minimum length

Cause: {0} has less than {1} characters

Action: Length should be at least {0} characters
Level: 1

Type: ERROR

Impact: Installation

INST-07036: Error in validating the {0} field value. Length greater than maximum length

Cause: {0} has more than {1} characters

Action: Length should not be greater than {0} characters
Level: 1

Type: ERROR

Impact: Installation

INST-07037: Error in validating the {0} field value. Invalid characters

Cause: {0} field value contains one or more invalid characters or the value is not in proper format.

Action: Enter valid characters
Level: 1

Type: ERROR

Impact: Installation

INST-07038: Error in validating the {0} field value. Invalid Start character

Cause: {0} field value contains one or more invalid start characters

Action: Enter valid start character
Level: 1

Type: ERROR

Impact: Installation

INST-07039: Error in validating the {0} field value

Cause: An unexpected error occurred while validating {0} field value

Action: Enter a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07040: Error in Password Check

Cause: Passwords entered were null or contained invalid characters

Action: Provide valid values
Level: 1

Type: ERROR

Impact: Installation

INST-07041: Error in Password Check

Cause: An unexpected error occurred while processing the handler

Action: Enter passwords that match
Level: 1

Type: ERROR

Impact: Installation

INST-07042: Error in Password Check. Password value null

Cause: Password value is null

Action: Enter a valid value for password
Level: 1

Type: ERROR

Impact: Installation

INST-07043: Error in Password Check. Confirm password value null.

Cause: Confirm Password value is null

Action: Enter a valid value for confirm password
Level: 1

Type: ERROR

Impact: Installation

INST-07044: Error in Password Check. Passwords do not match

Cause: Passwords entered do not match

Action: Enter identical passwords
Level: 1

Type: ERROR

Impact: Installation

INST-07045: Error in validating the {0} field value

Cause: An unexpected error occurred while validating {0} field value

Action: Enter a valid number
Level: 1

Type: ERROR

Impact: Installation

INST-07046: Error in validating the {0} field value

Cause: Provide a valid value for {0}

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07047: Error in validating the {0} field value. Not a number

Cause: {0} field value is not a number

Action: Enter a valid number
Level: 1

Type: ERROR

Impact: Installation

INST-07048: Error in Validating {0} and {1}

Cause: Values specified are null or contain invalid characters

Action: Provide valid values
Level: 1

Type: ERROR

Impact: Installation

INST-07049: Error in Validating {0} and {1}

Cause: An unexpected error occurred while validating {0} and {1}

Action: Enter values that do not match
Level: 1

Type: ERROR

Impact: Installation

INST-07050: Error in Validating {0} and {1}. Null Value

Cause: Provide a valid value for {0}

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07051: Error in Validating {0} and {1}. Values do not match

Cause: {0} and {1} are different

Action: Enter same values
Level: 1

Type: ERROR

Impact: Installation

INST-07052: Error in Validating {0} and {1}. Values match

Cause: {0} and {1} are the same

Action: Enter different values
Level: 1

Type: ERROR

Impact: Installation

INST-07053: Error in validating the {0} field value

Cause: {0} field value is null or contains invalid characters

Action: Provide valid values
Level: 1

Type: ERROR

Impact: Installation

INST-07054: Error in validating the {0} field value

Cause: An unexpected error occurred while validating {0} field value

Action: Enter a valid host name
Level: 1

Type: ERROR

Impact: Installation

INST-07055: Error in validating the {0} field value. Host name value null

Cause: Provide a valid value for {0}

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07056: Error in validating the {0} field value. Invalid host name

Cause: {0} field value is not a valid host name

Action: Enter a valid value for host name
Level: 1

Type: ERROR

Impact: Installation

INST-07057: Error in validating the {0} field value. Host is not up and running

Cause: Error in validating the {0} field value. Entered host is not up and running

Action: Make sure that the host is up and running
Level: 1

Type: ERROR

Impact: Installation

INST-07058: Error in validating Oracle home location

Cause: An unexpected error occurred while validating Oracle home location

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07059: Error in validating Oracle home location

Cause: Oracle home location Specified is missing. Provide a valid Oracle home location

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07060: Error in validating Oracle home location

Cause: The Oracle home location specified is not a valid {0} home location

Action: Provide a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07061: Error in obtaining default port file location

Cause: An unexpected error occurred while obtaining default port file location

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07062: Error in connecting to the Database

Cause: An unexpected error occurred while trying to connect to the Database

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07063: Error in connecting to the Database. Connect String is missing

Cause: Connect string is missing

Action: Provide a valid value for Connection String
Level: 1

Type: ERROR

Impact: Installation

INST-07064: Error in connecting to the Database

Cause: Unable to connect to the Database with the given credentials

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07065: Error in validating Database details

Cause: An unexpected error occurred while trying to connect to the Database

Action: Try again and check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07066: Error in validating Database details. Schema Type is missing

Cause: Schema type is missing

Action: Provide a valid value for Schema Type
Level: 1

Type: ERROR

Impact: Installation

INST-07067: Error in validating Database details. Schema name is missing

Cause: Schema is missing

Action: Provide a valid value for Schema Name
Level: 1

Type: ERROR

Impact: Installation

INST-07068: Error in validating Database details. Invalid Schema

Cause: Specified {0} schema does not exist in the given Database

Action: Check the schema name and the Database credentials
Level: 1

Type: ERROR

Impact: Installation

INST-07069: Validation of {0} location failed. Existing Oracle home

Cause: Validation of {0} location failed. The location specified is an existing Oracle home

Action: Provide an empty or nonexistent directory location
Level: 1

Type: ERROR

Impact: Installation

INST-07072: Error in validating Oracle home location

Cause: The Oracle home location specified is an existing Oracle home

Action: Provide an empty or nonexistent directory location
Level: 1

Type: ERROR

Impact: Installation

INST-07073: Error in validating Oracle home location

Cause: The Oracle home location specified is not a valid {0} home location

Action: Provide an empty or nonexistent directory location or a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07074: Error in validating Database details. Null Value

Cause: User name is missing

Action: Provide a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07075: Error in validating Database details. Invalid user

Cause: User does not have DBA privileges

Action: Provide a user with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07076: Error in validating Database details

Cause: An unexpected error occurred while trying to connect to the Database

Action: Try again and check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07077: Error in validating Oracle home and Oracle Instance home

Cause: Oracle home is inside the Oracle Instance home

Action: Enter a different location
Level: 1

Type: ERROR

Impact: Installation

INST-07078: Error in validating LDAP credentials

Cause: An unexpected error occurred while validating LDAP credentials

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07079: Error in validating LDAP credentials

Cause: Could not connect to LDAP with the given credentials.

Action: Verify the credentials. Make sure that hostname, port and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07080: Error in validating available disk space

Cause: Space required is missing or not a valid value

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07081: Error in validating available disk space

Cause: Insufficient space to install the selected components

Action: Specify a different Oracle home or increase disk space.
Level: 1

Type: ERROR

Impact: Installation

INST-07082: Error in validating available disk space

Cause: An unexpected error occurred while validating available disk space

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07083: Error in validating port file

Cause: Specified port file location is missing

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07084: Error in validating port file

Cause: Specified port file is invalid

Action: Specify a valid file
Level: 1

Type: ERROR

Impact: Installation

INST-07085: Error in validating port file

Cause: Specified port file does not exist

Action: Specify a valid file
Level: 1

Type: ERROR

Impact: Installation

INST-07086: Error in validating port file

Cause: An unexpected error occurred while parsing the port file

Action: Verify the file. Check if the values are provided in the proper format. There should be at least one section in the file.
Level: 1

Type: ERROR

Impact: Installation

INST-07087: Error in validating port file

Cause: An unexpected error occurred while validating port file

Action: Provide a valid value. Check if the values are provided in the proper format. There should be at least one section in the file.
Level: 1

Type: ERROR

Impact: Installation

INST-07093: Error in validating port file

Cause: Keys {0} does not have proper values

Action: Provide valid values. Ensure that the port is free, valid and it is not used by any other Oracle home
Level: 1

Type: ERROR

Impact: Installation

INST-07094: Error in validating port file

Cause: Ports {0} are not free or not valid

Action: Ensure that the port is free, valid and it is not used by any other Oracle home. If ports are specified using a file, check if proper values are given for key.
Level: 1

Type: ERROR

Impact: Installation

INST-07095: Error in validating port file

Cause: Key {0} does not have proper value

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07096: Required component not found in Oracle home

Cause: One or more of the required components required for the install options selected may be missing from the Oracle home

Action: Specify a valid Oracle home with all required Components
Level: 1

Type: ERROR

Impact: Installation

INST-07097: Error in validating component name

Cause: Component name specified is not correct

Action: Provide a valid component name
Level: 1

Type: ERROR

Impact: Installation

INST-07098: Error in validating Oracle home location

Cause: Component {0} is not available in the Oracle home but selected for configuration.

Action: Deselect the above component for configuration
Level: 1

Type: ERROR

Impact: Installation

INST-07099: Error in validating Oracle home location

Cause: Components {0} are not available in the Oracle home but selected for configuration.

Action: Deselect the above components for configuration
Level: 1

Type: ERROR

Impact: Installation

INST-07100: Error in validating port file

Cause: Port {0} is duplicated

Action: Provide different ports
Level: 1

Type: ERROR

Impact: Installation

INST-07101: Error in validating port file

Cause: Ports {0} are duplicated

Action: Provide different ports
Level: 1

Type: ERROR

Impact: Installation

INST-07102: Error in validating port file

Cause: Port {0} is already used by existing Oracle homes

Action: Provide a port which is valid and free
Level: 1

Type: ERROR

Impact: Installation

INST-07103: Error in validating port file

Cause: Ports {0} are already used by existing Oracle homes

Action: Provide port values which are valid and free
Level: 1

Type: ERROR

Impact: Installation

INST-07104: Error in validating port file

Cause: Key {0} should not be specified as a range

Action: Provide a single port which is valid and free
Level: 1

Type: ERROR

Impact: Installation

INST-07105: Error in validating port file

Cause: Key {0} should not be specified as a range

Action: Provide single port values which are valid and free
Level: 1

Type: ERROR

Impact: Installation

INST-07106: Error in validating port file

Cause: Port {0} is not free or not valid

Action: Ensure that the port ( a number between 0 - 65535 ) is free and it is not used by any other Oracle home. If ports are specified using a file, check if proper values are given for key
Level: 1

Type: ERROR

Impact: Installation

INST-07107: Error in validating port value

Cause: An unexpected error occurred while validating port value

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07108: Error in validating components selected for configuration

Cause: An unexpected error occurred while processing the handler

Action: Select valid components
Level: 1

Type: ERROR

Impact: Installation

INST-07109: Error in validating components selected for configuration

Cause: At least one component should be selected for configuration

Action: Select at least one component for configuration
Level: 1

Type: ERROR

Impact: Installation

INST-07110: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service id

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07111: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service name

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07112: Error in obtaining schema details

Cause: An unexpected error occurred while trying to get schema details

Action: Try executing again and check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07113: Error in obtaining schema details

Cause: Error in validating schema details. Could not fetch schema details from database

Action: Try executing again and check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07114: Error in obtaining schema details

Cause: Error in validating schema details. Schema Registry table does not exist

Action: Provide a Database which has schemas loaded
Level: 1

Type: ERROR

Impact: Installation

INST-07115: Error in validating {0} schema details

Cause: An unexpected error occurred while validating {0} schema details

Action: Try again and check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07119: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Listener could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07120: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid user name/password

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07121: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. User is not a SYSDBA

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07122: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Database could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07123: Error in validating port file

Cause: Specified file is empty or does not contain valid entries

Action: Provide a valid file
Level: 1

Type: ERROR

Impact: Installation

INST-07124: Error in validating Oracle home location

Cause: Component {0} is not available in the Oracle home but selected for installation.

Action: Deselect the above component
Level: 1

Type: ERROR

Impact: Installation

INST-07125: Error in validating Oracle home location

Cause: Components {0} are not available in the Oracle home but selected for installation.

Action: Deselect the above components
Level: 1

Type: ERROR

Impact: Installation

INST-07132: Error in validating jpsRootDN value

Cause: User(s) {0} are not present in the specified LDAP

Action: Users "fmwadmin" and "systemuser" must be present. The user must also have privileges to create users and groups
Level: 1

Type: ERROR

Impact: Installation

INST-07133: Error in obtaining LDAP bindpass

Cause: User {0} does not have permission to create {1}

Action: Users "fmwadmin" and "systemuser" must be present. The user must also have privileges to create users and groups
Level: 1

Type: ERROR

Impact: Installation

INST-07134: Error in validating Oracle Configuration Manager Service credentials

Cause: Customer Identification Number is missing or invalid

Action: Provide a valid value for Customer Identification Number
Level: 1

Type: ERROR

Impact: Installation

INST-07135: Error in validating Oracle Configuration Manager Service credentials

Cause:

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07136: Error in validating Oracle Configuration Manager Service credentials

Cause: Country Code value is incorrect

Action: Provide a valid value for Country Code
Level: 1

Type: ERROR

Impact: Installation

INST-07137: Error in validating Oracle Configuration Manager Service credentials

Cause: Could not connect Oracle Configuration Manager Service with the specified credentials

Action: Verify the values. Make sure the Customer Identification Number, My Oracle Support User Name and the Country code are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07138: Error in validating Oracle Configuration Manager Service credentials

Cause: An unexpected error occurred while validating the Oracle Configuration Manager Service credentials

Action: Verify the values and try again
Level: 1

Type: ERROR

Impact: Installation

INST-07139: Error in validating Oracle Configuration Manager Service credentials

Cause: Provide a valid value for Customer Identification Number

Action: CSI number must contain numeric characters only
Level: 1

Type: ERROR

Impact: Installation

INST-07144: Error in validating LDAP Credentials

Cause: Specified LDAP Type ( {0} ) is not valid

Action: Valid values are "{0}". Enter a valid LDAP Type
Level: 1

Type: ERROR

Impact: Installation

INST-07150: Error in validating jpsRootDN value

Cause: Specified JPS Root DN value is not valid

Action: Provide a valid value. Make sure that the root DN provided is an empty container.
Level: 1

Type: ERROR

Impact: Installation

INST-07151: Error in validating jpsRootDN value

Cause: Provide a valid value for JPS Root DN

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07152: Error in obtaining LDAP Host

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07153: Error in obtaining LDAP Port

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07154: Error in obtaining LDAP binddn

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07155: Error in obtaining LDAP bindpass

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07156: Error in validating URL

Cause: Provide a valid value the URL

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07157: Error in validating URL

Cause: URL {0} is not valid

Action: Provide a valid URL in [hostname.domainname:port] format and make sure the given URL is accessible
Level: 1

Type: ERROR

Impact: Installation

INST-07158: Error in validating URL

Cause: URL {0} is not accessible.

Action: Provide a valid URL which is accessible.
Level: 1

Type: ERROR

Impact: Installation

INST-07159: Error in validating URL

Cause: An unexpected error occurred while validating the URL

Action: Verify the values and try again
Level: 1

Type: ERROR

Impact: Installation

INST-07169: Error in validating port file

Cause: Port range {0} is not valid. Start range is greater than end range

Action: Provide a valid port range
Level: 1

Type: ERROR

Impact: Installation

INST-07172: Error in validating port file

Cause: Key {0} is missing in the section [{1}]

Action: Provide a value for the key
Level: 1

Type: ERROR

Impact: Installation

INST-07173: Error in validating port file

Cause: Keys {0} are missing in the section [{1}]

Action: Provide valid value for the keys
Level: 1

Type: ERROR

Impact: Installation

INST-07174: Error in validating port file

Cause: Key {0} is not valid in the section [{1}]

Action: Valid keys for section [{0}] are {1}
Level: 1

Type: ERROR

Impact: Installation

INST-07175: Error in validating port file

Cause: Keys {0} were not valid in the section [{1}]

Action: Valid keys for section [{0}] are {1}
Level: 1

Type: ERROR

Impact: Installation

INST-07176: Error in validating port file

Cause: Key {0} is duplicated

Action: Remove duplicate entries
Level: 1

Type: ERROR

Impact: Installation

INST-07177: Error in validating port file

Cause: Keys {0} are duplicated

Action: Remove duplicate entries
Level: 1

Type: ERROR

Impact: Installation

INST-07179: Error in validating port file

Cause: Port range {0} are not valid. Start range is greater than end range

Action: Provide a valid port range
Level: 1

Type: ERROR

Impact: Installation

INST-07180: Error in validating port file

Cause: Specified Port range {0} does not have free port.

Action: Provide a different range. Check if the same range is mentioned more than once in the file.
Level: 1

Type: ERROR

Impact: Installation

INST-07181: Error while obtaining registry key value

Cause: An error occurred while obtaining a registry key value

Action: Provide a valid value for Registry Key
Level: 1

Type: ERROR

Impact: Installation

INST-07182: Error while obtaining registry key value

Cause: An error occurred while obtaining a registry key value

Action: Provide a valid value for Registry Sub Key
Level: 1

Type: ERROR

Impact: Installation

INST-07183: Error while obtaining registry key value

Cause: An error occurred while obtaining a registry key value

Action: Provide a valid value for Registry Property Name
Level: 1

Type: ERROR

Impact: Installation

INST-07184: Error while obtaining registry key value

Cause: An unexpected error occurred while obtaining registry key value

Action: Verify the values and try again
Level: 1

Type: ERROR

Impact: Installation

INST-07185: Error in validating proxy credentials

Cause: Provide a valid value for Proxy Server

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07186: Error in validating proxy credentials

Cause: Provide a valid value for Proxy Port

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07187: Error in validating proxy credentials

Cause: Specified Proxy port is not a valid value

Action: Provide a valid number for Proxy Port
Level: 1

Type: ERROR

Impact: Installation

INST-07188: Error in validating proxy credentials

Cause: Could not establish connection to the specified proxy credentials

Action: Verify the values. Make sure the proxy server, proxy port values are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07189: Error in validating proxy credentials

Cause: An unexpected error occurred while obtaining registry key value

Action: Verify the values and try again
Level: 1

Type: ERROR

Impact: Installation

INST-07202: Error in validating container name

Cause: Provide a valid value for container name

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07203: Error in validating container name

Cause: Specified value is a reserved key word.

Action: Provide value other than {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07204: Error in validating container name

Cause: An unexpected error occurred while validating the URL

Action: Verify the values and try again
Level: 1

Type: ERROR

Impact: Installation

INST-07205: Error in validating port file

Cause: Port {0} is duplicated for keys {1}

Action: Provide different ports
Level: 1

Type: ERROR

Impact: Installation

INST-07206: Error in validating port file

Cause: Port {0} (JMX Port No + 1 ) is not free

Action: JMX Port No + 1 will be used as Java Object Cache Local Port No. Specify a value for Java Object Cache Local Port No key or provide a JMX Port No which has also (JMX Port No + 1 ) free
Level: 1

Type: ERROR

Impact: Installation

INST-07207: Error in validating port file

Cause: Port {0} (JMX Port No + 2 ) is not free

Action: JMX Port No + 2 will be used as Java Object Cache Remote Port No. Specify a value for Java Object Cache Remote Port No key or provide a JMX Port No which has also (JMX Port No + 2 ) free
Level: 1

Type: ERROR

Impact: Installation

INST-07208: Error in validating port file

Cause: Reserved ports are not allowed under section [{0}]. Key(s) {1} have Operating System reserved port entries.

Action: Provide different port(s)
Level: 1

Type: ERROR

Impact: Installation

INST-07210: Error in obtaining 10g SSO information

Cause: An unexpected error occurred while obtaining 10g SSO information

Action: Verify the LDAP credentials. Make sure that hostname, port, binddn, password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07211: Error in obtaining Oracle Internet Directory version

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07212: Error in checking the version of Oracle Internet Directory

Cause: Version of the given Oracle Internet Directory is not {0}

Action: Provide an alternate Oracle Internet Directory location
Level: 1

Type: ERROR

Impact: Installation

INST-07213: Error in checking the version of Oracle Internet Directory

Cause: An unexpected error occurred while checking the version of Oracle Internet Directory

Action: Verify the LDAP credentials. Make sure that hostname, port, binddn, password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07214: Error in validating URL

Cause: Specified URL is not valid

Action: Provide a valid value for the URL
Level: 1

Type: ERROR

Impact: Installation

INST-07215: Error in validating URL

Cause: Specified URL is not correct format

Action: Provide a valid URL
Level: 1

Type: ERROR

Impact: Installation

INST-07216: Error in validating URL

Cause: Specified URL is not accessible

Action: Provide a valid URL
Level: 1

Type: ERROR

Impact: Installation

INST-07217: Error in validating URL

Cause: Specified URL is not accessible

Action: Provide a valid URL
Level: 1

Type: ERROR

Impact: Installation

INST-07221: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:servicename , For Real Application Cluster Database hostname1:port1îhostname2:port2@servicename
Level: 1

Type: ERROR

Impact: Installation

INST-07222: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:sid , For a Real Application Cluster Database, use hostname1:port1îhostname2:port2@servicename
Level: 1

Type: ERROR

Impact: Installation

INST-07223: Error in obtaining work repository details

Cause: Work repository table does not exist

Action: Provide a Database which has repositories loaded
Level: 1

Type: ERROR

Impact: Installation

INST-07224: Error in obtaining work repository details

Cause: Error in obtaining work repository details. Could not fetch repository details from database

Action: Try executing again and check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07225: Error in validating work repository details

Cause: An unexpected error occurred while validating work repository details

Action: Try again and check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07226: Error in validating Database details. Invalid Work Repository

Cause: Specified {0} repository does not exist in the given Database

Action: Check the {0} repository name and the Database credentials
Level: 1

Type: ERROR

Impact: Installation

INST-07227: Error in validating work repository details

Cause: Provide a valid {0} repository name

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07228: Error in connecting to the Database

Cause: Unable to connect to the Database with the given credentials

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07229: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Listener could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07230: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid user name/password

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07231: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. User is not a SYSDBA

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07232: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Database could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07233: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service id

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07234: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service name

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07235: Error in validating the {0} field value

Cause: Please enter the {0} field value in the range {1} - {2}

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07236: Error in validating the agent name

Cause: Provide a valid value for the agent name

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07237: Error in validating the agent name

Cause: Agent name already exists. Provide a different value

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07238: Error in validating the agent name

Cause: Unable to verify the agent name

Action: Verify the values. Make sure the Master Database is up and running and connect string, user name, password, ODI supervisor username and ODI supervisor password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07239: Error in validating Database details. Invalid Schema

Cause: Not able to connect to the specified {0} Schema

Action: Check the schema name and the Database credentials
Level: 1

Type: ERROR

Impact: Installation

INST-07240: Error in obtaining {0}components from Oracle WebLogic Middleware Administration Server.

Cause: Error in obtaining {0}components from Oracle WebLogic Middleware Administration Server.

Action: Check the given credentials. Make sure the Oracle WebLogic Middleware Administration Server is up and hostname, port, user name and administration password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07241: Error in obtaining connection with Oracle WebLogic Middleware Administration Server

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server. Credentials entered are null or contains invalid characters

Action: Make sure the Middleware Administration Server is up and hostname, port, user name and administration password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07242: Error in obtaining connection with Oracle WebLogic Middleware Administration Server

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server.

Action: Make sure the Oracle Middleware Administration Server is up and hostname, port, user name and administration password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07243: Unable to connect to Oracle WebLogic Middleware Administration Server. Hostname is missing.

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server. Hostname is missing.

Action: Enter a valid hostname
Level: 1

Type: ERROR

Impact: Installation

INST-07244: Unable to connect to Oracle WebLogic Middleware Administration Server. Port number is missing.

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server. Port number is missing.

Action: Enter a valid port
Level: 1

Type: ERROR

Impact: Installation

INST-07245: Unable to connect Oracle WebLogic Middleware Administration Server. Admin User name is missing.

Cause: Unable to connect Oracle WebLogic Middleware Administration Server. Admin User name is missing.

Action: Enter a valid admin user name
Level: 1

Type: ERROR

Impact: Installation

INST-07246: Error in validating {0} home location

Cause: Enter a valid value for {0} home location

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07247: Error in validating {0} home location

Cause: Specified {0} home location is either not valid or missing

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07248: Error in validating {0} home location

Cause: Specified {0} home location is not a valid location

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07249: Error in validating {0} home location

Cause: An unexpected error occurred during the validation of {0} home location

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07250: Error in validating Middleware home and WebLogic home

Cause: Specified WebLogic home is not associated with the given Middleware home

Action: Enter a WebLogic home which is associated with the specified Oracle Middleware home
Level: 1

Type: ERROR

Impact: Installation

INST-07251: Error in validating Middleware home and WebLogic home

Cause: An unexpected error occurred during the validation of Oracle Middleware home and WebLogic home

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07252: Error while obtaining default Middleware home and WebLogic home directories

Cause: An unexpected error occurred while obtaining default Oracle Middleware home and WebLogic home directories

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07253: Error in validating instance name

Cause: Specified instance name is not a valid instance name

Action: Enter a valid instance name associated with the specified instance home
Level: 1

Type: ERROR

Impact: Installation

INST-07254: Error in validating instance name

Cause: An unexpected error occurred during the validation of instance name

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07255: Error in validating instance name

Cause: instance name is incorrect

Action: Enter a valid value for instance name
Level: 1

Type: ERROR

Impact: Installation

INST-07256: Error in validating {0} component name

Cause: Component type failed validation

Action: Enter a valid value for {0} component name
Level: 1

Type: ERROR

Impact: Installation

INST-07257: Error in validating component type

Cause: Component type failed validation

Action: Enter a valid value for component type
Level: 1

Type: ERROR

Impact: Installation

INST-07258: Error in validating component name

Cause: An unexpected error occurred during the validation of component name

Action: Verify the instance home location
Level: 1

Type: ERROR

Impact: Installation

INST-07259: Error in validating {0} component name

Cause: Specified value for {0} component name already exists

Action: Provide a different value
Level: 1

Type: ERROR

Impact: Installation

INST-07260: Error in validating {0} component name

Cause: Specified value for {0} component name is not valid. A directory with the same name already exists under INST_HOME/config/{0}

Action: Provide a different value
Level: 1

Type: ERROR

Impact: Installation

INST-07261: Error in validating component name

Cause: Specified component name is not a valid component name

Action: Enter a valid component name associated with the specified instance
Level: 1

Type: ERROR

Impact: Installation

INST-07262: Error in validating instance details in the domain

Cause: Specified instance details are not valid

Action: Enter a valid instance name available in the domain. Make sure the instance home entered is in conjunction with the instance name.
Level: 1

Type: ERROR

Impact: Installation

INST-07263: Error in validating instance name

Cause: Specified instance name is not valid

Action: Enter a valid instance name available in the domain.
Level: 1

Type: ERROR

Impact: Installation

INST-07264: Error in validating instance details in the domain

Cause: An unexpected error occurred during the validation of instance details

Action: Check the values. Verify the instance name and instance home location
Level: 1

Type: ERROR

Impact: Installation

INST-07265: Error in validating instance name

Cause: An unexpected error occurred during the validation of instance name

Action: Check the values. Verify the instance name
Level: 1

Type: ERROR

Impact: Installation

INST-07266: Error in validating component name in the domain

Cause: Specified {0} component name already exists in the domain

Action: Provide a different value
Level: 1

Type: ERROR

Impact: Installation

INST-07267: Error in validating component name in the domain

Cause: An unexpected error occurred during the validation of component name

Action: Check the values. Verify the component name
Level: 1

Type: ERROR

Impact: Installation

INST-07268: Error in validating component name in the domain

Cause: Specified {0} component name does not exist in the domain

Action: Enter an existing component name
Level: 1

Type: ERROR

Impact: Installation

INST-07269: Error while obtaining default values for instance name and instance location

Cause: An unexpected error occurred while obtaining default values for instance name and instance location

Action: Check the values and try again
Level: 1

Type: ERROR

Impact: Installation

INST-07270: Error in validating instance name in the domain

Cause: Specified instance name already exists in the domain

Action: Provide a different value
Level: 1

Type: ERROR

Impact: Installation

INST-07271: Error in validating instance name in the domain

Cause: An unexpected error occurred during the validation of instance name

Action: Check the values. Verify the instance name
Level: 1

Type: ERROR

Impact: Installation

INST-07272: Error while obtaining the component names from the instance home

Cause: An unexpected error occurred while obtaining the component names from the instance home

Action: Check the values. Verify the instance home location
Level: 1

Type: ERROR

Impact: Installation

INST-07273: Error while obtaining the component names of a given component type from the instance home

Cause: An unexpected error occurred while obtaining the component names of a given component type from the instance home

Action: Check the values. Verify the instance home location
Level: 1

Type: ERROR

Impact: Installation

INST-07274: Error in validating port value

Cause: Port {0} is not valid. Privileged ports are not allowed

Action: Provide a different value
Level: 1

Type: ERROR

Impact: Installation

INST-07275: Error in validating {0} home location

Cause: Specified {0} home location does not have read/write permissions

Action: Provide read/write permissions for the {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07276: Error in validating {0} home location

Cause: Enter a valid value for {0} home location

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07277: Error in validating {0} name

Cause: Specified {0} name is either not valid or the corresponding location is not empty

Action: Enter a valid {0} name
Level: 1

Type: ERROR

Impact: Installation

INST-07278: Error in validating {0} home location

Cause: Specified {0} home location does not have Read/Write permissions

Action: Provide Read/Write permissions for the specified {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07279: Error in validating {0} home location

Cause: An unexpected error occurred during the validation of {0} home location

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07280: Error in validating domain credentials

Cause:

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07281: Error in validating domain credentials

Cause: {0} is not set up in the specified domain

Action: Enter a domain which has {0} set up
Level: 1

Type: ERROR

Impact: Installation

INST-07282: Error in validating {0} home location

Cause: Specified {0} home location does not exist

Action: Provide an existing {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07283: Error in validating My Oracle Support Details

Cause: Specified My Oracle Support Details are not proper

Action: Enter valid values
Level: 1

Type: ERROR

Impact: Installation

INST-07284: Error in validating My Oracle Support Details

Cause: An unexpected error occurred while validating My Oracle Support Details

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07285: Error in validating Database details. Invalid Schema

Cause: The schema name {0} and schema type {1} do not match

Action: Provide a valid schema name for {1}
Level: 1

Type: ERROR

Impact: Installation

INST-07286: Error in validating Middleware home location

Cause: Specified Oracle Middleware home location does not have minimum version {0} of WebLogic server. If the version is incorrect then configuring with the Weblogic server will fail.

Action: Provide a Oracle Middleware home location which contains WebLogic server with minimum version {0} or upgrade the Weblogic server to {0} or higher version and restart the install.
Level: 1

Type: ERROR

Impact: Installation

INST-07287: Error in obtaining connection with Oracle WebLogic Middleware Administration Server

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server. Server is not running.

Action: Make sure the Middleware Administration Server is up
Level: 1

Type: ERROR

Impact: Installation

INST-07288: Error in obtaining connection with Oracle WebLogic Middleware Administration Server

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server. Invalid username/password

Action: Enter a valid username and password
Level: 1

Type: ERROR

Impact: Installation

INST-07289: Error in validating WebLogic Server Directory

Cause: Specified WebLogic Server Directory is either not valid or empty

Action: Enter a valid WebLogic Server Directory
Level: 1

Type: ERROR

Impact: Installation

INST-07290: Error in validating Oracle home location

Cause: Specified Middleware home already has a {0} home. Only one {0} home location can reside under a Middleware home.

Action: Provide a different Middleware home location
Level: 1

Type: ERROR

Impact: Installation

INST-07291: Error in validating Oracle home location

Cause: Top Component name specified is null.

Action: Provide a valid component name
Level: 1

Type: ERROR

Impact: Installation

INST-07292: Error in validating Middleware home location

Cause: Middleware home location specified is not a valid location. Provide a valid Middleware home location

Action: Provide a valid Middleware home location.
Level: 1

Type: ERROR

Impact: Installation

INST-07293: Error in validating SSO credentials

Cause: Given OID does not have a proper SSO.

Action: Provide an OID with a 10g SSO.
Level: 1

Type: ERROR

Impact: Installation

INST-07294: Error in validating SSO credentials

Cause: Could not retrieve SSO information with the given credentials.

Action: Verify the credentials. Make sure that hostname, port and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07295: Error in validating UCM Installer Location

Cause: Specified UCM Installer Location is not valid

Action: Provide a valid value for UCM Installer Location.
Level: 1

Type: ERROR

Impact: Installation

INST-07296: Error in validating UCM Installer Location

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07297: Error in validating Web Server HTTP Address

Cause: Webserver HTTP Address is missing

Action: Provide a valid value for Webserver HTTP Address
Level: 1

Type: ERROR

Impact: Installation

INST-07298: Error in validating Web Server HTTP Address

Cause: Specified Web Server HTTP Address is not valid

Action: The Web Server HTTP Address has to be in http(s)://[host]:[port]?/[webroot] format
Level: 1

Type: ERROR

Impact: Installation

INST-07299: Error in validating Web Server HTTP Address

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07300: Error in validating UCM Installer Location

Cause: UCM Installer Location is missing

Action: Provide a valid value for UCM Installer Location
Level: 1

Type: ERROR

Impact: Installation

INST-07301: Error in validating UCM Installer Location

Cause: Specified UCM Installer Location is empty

Action: Provide a valid value for UCM Installer Location.
Level: 1

Type: ERROR

Impact: Installation

INST-07302: Error in validating Domain

Cause: Specified domain cannot be used for Expand Cluster configuration

Action: Specify a domain which has clusters
Level: 1

Type: ERROR

Impact: Installation

INST-07303: Error in validating Domain

Cause: Specified domain cannot be used for Extend Domain configuration

Action: Specify a domain which has at least one component not configured
Level: 1

Type: ERROR

Impact: Installation

INST-07304: Validation of User Name failed. Invalid User Name

Cause: The user name entered is not valid

Action: Provide a valid user name
Level: 1

Type: ERROR

Impact: Installation

INST-07305: Validation of password value failed. Invalid password

Cause: The password entered is not valid

Action: Provide a valid password
Level: 1

Type: ERROR

Impact: Installation

INST-07306: Error in validating Database details. RAC Dabase is not supported

Cause: RAC Database is not supported for {0}

Action: {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07307: Error in validating Oracle home location

Cause: Oracle home location specified is not inside Middleware home location. Provide a valid location for Oracle home.

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07308: Oracle Universal Content Management is already installed and configured at location {0}

Cause: Oracle Universal Content Management is already installed and configured at location {0}

Action: Either select not to configure again or uninstall Oracle Universal Content Management and then try to reconfigure
Level: 1

Type: ERROR

Impact: Installation

INST-07309: Error in validating master repository details

Cause: Specified Master Repository credentials are not valid.

Action: Verify the values. Make sure the Master Database is up and running and connect string, user name, password, ODI supervisor username and ODI supervisor password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07310: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:servicename
Level: 1

Type: ERROR

Impact: Installation

INST-07311: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:sid
Level: 1

Type: ERROR

Impact: Installation

INST-07312: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:servicename , For Real Application Cluster Database hostname1:port1îhostname2:port2@servicename
Level: 1

Type: ERROR

Impact: Installation

INST-07313: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:sid , For a Real Application Cluster Database, use hostname1:port1îhostname2:port2@servicename
Level: 1

Type: ERROR

Impact: Installation

INST-07314: Error in validating port file

Cause: Port {0} is not valid

Action: Provide a valid port number ( a number between {0} )
Level: 1

Type: ERROR

Impact: Installation

INST-07315: Error in validating port value

Cause: An unexpected error occurred while validating port value

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07316: Error in validating port file

Cause: Port {0} is not free or not valid

Action: Ensure that the port ( a number between 1024 - 65535 ) is free and it is not used by any other Oracle home. If ports are specified using a file, check if proper values are given for key.
Level: 1

Type: ERROR

Impact: Installation

INST-07317: Validation of {0} location failed. Directory does not exist.

Cause: Validation of {0} location failed. The location specified does not exist.

Action: Enter a valid existing directory
Level: 1

Type: ERROR

Impact: Installation

INST-07318: Validation of {0} location failed. Directory s empty.

Cause: Validation of {0} location failed. The location specified is empty.

Action: Enter a nonempty directory
Level: 1

Type: ERROR

Impact: Installation

INST-07319: Validation of {0} location failed. Directory already exists and is not a valid Oracle Home directory.

Cause: Validation of {0} location failed. The location specified already exists and is a nonempty directory and not a valid Oracle Home

Action: Provide an empty or nonexistent directory location, or a valid existing Oracle Home
Level: 1

Type: ERROR

Impact: Installation

INST-07404: Error in validating Oracle home

Cause: Specified Oracle home value is null

Action: Specify the correct Oracle home name
Level: 1

Type: ERROR

Impact: Installation

INST-07405: Error in validating Oracle home

Cause: The specified Oracle home does not match with the Domain Oracle home

Action: Specify Oracle home name same as that of the Domain Oracle home
Level: 1

Type: ERROR

Impact: Installation

INST-07406: Error in validating {0} home location

Cause: Specified {0} home location is either not valid or is empty

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07407: Error in detecting machine platform or JVM bits.

Cause: Unable to detect machine platform or JVM bits.

Action: Make sure machine platform and JVM are supported.
Level: 1

Type: ERROR

Impact: Installation

INST-07408: Cannot install or configure the product on a 32-bit JVM on a 64-bit machine.

Cause: Unable to install or configure the product on a 32-bit JVM on a 64-bit machine.

Action: Make sure to install and configure the product in supported modes.
Level: 1

Type: ERROR

Impact: Installation

INST-07409: Error in validating instance name

Cause: Unexpected error in validating instance name

Action: Make sure entered values are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07410: Error in validating instance name

Cause: Specified instance name is not valid, a windows service with the specified instance name already exists

Action: Provide a different instance name
Level: 1

Type: ERROR

Impact: Installation

INST-07411: Error in validating oracle home

Cause: Provide valid value for Oracle Home Directory.

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07412: Error in validating oracle home

Cause: Oracle Home Directory name cannot be oracle_common.

Action: Provide a different value for Oracle Home Directory.
Level: 1

Type: ERROR

Impact: Installation

INST-07413: Error in validating oracle home

Cause: Unexpected error in validating Oracle Home Directory

Action: Make sure entered values are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07414: Error in validating {0}

Cause: Specified {0} is not valid

Action: Provide a valid value {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07415: Error in validating Home Type

Cause: Home Type Specified is not Correct

Action: Provide a valid a valid Home Type
Level: 1

Type: ERROR

Impact: Installation

INST-07416: Error in validating {0}

Cause: An unexpected error occurred while validating {0}

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07417: Error in validating the {0}

Cause: {0} has not been installed in the specified {1}. Provide a different Location

Action: Provide a different {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07420: Error in validating oracle home

Cause: Oracle Home Directory name cannot be {0}.

Action: Provide a different value for Oracle Home Directory.
Level: 1

Type: ERROR

Impact: Installation

INST-07421: Error in executing the software update flow

Cause: An error occurred while validating the values for software updates

Action: Make sure entered values are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07422: Error in validating library

Cause: The library {0} does not exists in the provided location

Action: Make sure the library {0} exists in the provided location
Level: 1

Type: ERROR

Impact: Installation

INST-07423: Error in validating library

Cause: The library {0} does not exists in the provided location

Action: Make sure the library {0} exists in the provided location
Level: 1

Type: ERROR

Impact: Installation

INST-07424: Error in validating library

Cause: The version of library at the provided location is not as expected

Action: Make sure the version of library at the provided location is correct
Level: 1

Type: ERROR

Impact: Installation

INST-07425: Error in verifying version of Application Server

Cause: Could not access versionInfo script under the Application Server Directory provided

Action: Make sure the the Application Server directory has versionInfo script under bin folder
Level: 1

Type: ERROR

Impact: Installation

INST-07426: Error in verifying version of Application Server

Cause: The version of Application Server is not valid

Action: Make sure the the version of Application Server is at least {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07427: Error in verifying Application Server

Cause: The Application Server Directory does not refer to WebSphere Application Server

Action: Provide the directory location of WebSphere Application Server
Level: 1

Type: ERROR

Impact: Installation

INST-07440: Error in validating Application Server Type

Cause: Validation of Application Server Type failed. Supported Application Server Types are WLS and WAS.

Action: Specify a valid Application Server Type. Supported Application Server Types are WLS and WAS.
Level: 1

Type: ERROR

Impact: Installation

INST-07441: Error in validating Application Server Type

Cause: Validation of Application Server Type failed. Specified Application Server Type does not match with the Application Server detected in the Middleware home.

Action: Specify a valid Application Server Type.
Level: 1

Type: ERROR

Impact: Installation

INST-07509: Error in validating master repository details

Cause: Specified Master Repository schema details are not valid.

Action: Verify the values. Make sure the Master Database schema version is correct and master repository is created with appropriate Repository Creation Utility.
Level: 1

Type: ERROR

Impact: Installation

INST-07520: Error in validating {0} location

Cause: Enter a valid value for {0} location

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07521: Error in validating {0} home location

Cause: Specified {0} home location does not exist

Action: Provide an exisiting {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07522: Error in validating {0} home location

Cause: Specified {0} home location does not have read/write permissions

Action: Provide read/write permissions for the {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07523: Error in validating {0} home location

Cause: Specified {0} home location is either not valid or empty

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07524: Error in validating {0} home location

Cause: Specified {0} home location is not a valid location

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07525: Error in validating {0} home location

Cause: An unexpected error occurred during the validation of {0} home location

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07526: Error in validating {0} home location

Cause: Specified {0} home location is not a valid location

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07527: Error in validating Middleware home location

Cause: Specified Oracle Middleware home location does not have appropriate version of WebLogic server

Action: Provide a Oracle Middleware home location which contains WebLogic server with a supported version
Level: 1

Type: ERROR

Impact: Installation

INST-07528: Validation of {0} location failed. Directory does not exist.

Cause: Validation of {0} location failed. The location specified does not exist.

Action: Enter a valid existing directory
Level: 1

Type: ERROR

Impact: Installation

INST-07529: Error in validating Farm Name

Cause: Farm Name cannot be {0}.

Action: Enter a different Farm Name.
Level: 1

Type: ERROR

Impact: Installation

INST-07530: Patchset component found in Oracle home

Cause: This Patchset has already been applied to the Oracle home

Action: Specify an Oracle home where the patchset has not already been applied.
Level: 1

Type: ERROR

Impact: Installation

INST-07531: Error in validating contents of Oracle home

Cause: The Oracle home provided does not contain {0}.

Action: In order to patch your existing version please provide an Oracle home that contains the product mentioned above. If you choose to continue, only the oracle_common directory and any components that both products have in common will be patched.
Level: 1

Type: ERROR

Impact: Installation

INST-07532: Error in validating contents of Oracle home

Cause: The Oracle home provided does not contain {0}.

Action: In order to patch your existing version please provide an Oracle home that contains the product mentioned above. If you choose to continue, only the oracle_common directory and any components that both products have in common will be patched.
Level: 1

Type: ERROR

Impact: Installation

INST-07533: Error in validating Middleware home location

Cause: Middleware home location specified is missing.

Action: Provide a valid Middleware home location
Level: 1

Type: ERROR

Impact: Installation

INST-07534: Error in validating Oracle home location

Cause: Oracle home location specified is not inside Middleware home location. Provide a directory name only for Oracle home.

Action: Provide a different Oracle home location which is inside Middleware home.
Level: 1

Type: ERROR

Impact: Installation

INST-07535: Error in obtaining hostname

Cause: An unexpected error occurred while retrieving hostname

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07536: Error in validating Oracle home location

Cause: Middleware home location specified does not have the required Oracle homes installed in it. The Oracle homes for the following components are not installed: {0}.

Action: Provide a different Middleware home location or install the required Oracle Products and try the install again
Level: 1

Type: ERROR

Impact: Installation

INST-07537: The weblogic server processes are still running.

Cause: Unable to install while the weblogic processes are running.

Action: Make sure that the node manager and the weblogic servers are shutdown before the installation.
Level: 1

Type: ERROR

Impact: Installation

INST-07538: The OPMN processes are still running.

Cause: Unable to install while the OPMN processes are running.

Action: Make sure that opmnctl stopall is run before the installation.
Level: 1

Type: ERROR

Impact: Installation

INST-07539: {0} found in Oracle home

Cause: This Oracle home already contains a version of {0} which cannot be updated by this installation

Action: Specify either a new Oracle Home Directory or an Oracle Home which can be updated by this installer.
Level: 1

Type: ERROR

Impact: Installation

INST-07540: Missing Dependent Feature sets in {0}

Cause: Enter a valid {0} which has all required dependent featuresets

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07541: Error in validating Feature set Dependencies in {0}

Cause: Unexpected Error

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07542: Error in validating Oracle Home location.

Cause: The distribution {0} is not installed in the given Oracle Home.

Action: Choose a different Oracle Home location.
Level: 1

Type: ERROR

Impact: Installation

INST-07543: Error in validating Oracle Home location.

Cause: {0} cannot be installed in an Oracle Home that has {1} already installed.

Action: Choose a different Oracle Home location.
Level: 1

Type: ERROR

Impact: Installation

INST-07544: Error in validating Oracle Home location.

Cause: Oracle Home provided is null or empty

Action: Provide a different Oracle Home location.
Level: 1

Type: ERROR

Impact: Installation

INST-07545: Error in validation. Unexpected Error

Cause: Unexpected Error. {0}

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07546: Error in validating installation type.

Cause: Unable to find install type {0}

Action: Provide a valid install type
Level: 1

Type: ERROR

Impact: Installation

INST-07547: Incompatible installation type.

Cause: Incompatible installation type provided. {0}

Action: Select a valid install type. Check http://docs.oracle.com/cd/E23104_01/download_readme.htm for details about compatible products and install types.
Level: 1

Type: ERROR

Impact: Installation

INST-07548: No compatible installation type found.

Cause: The selected distribution does not have any compatible install type for the selected Oracle Home.

Action: Provide a different oracle Home. Check http://docs.oracle.com/cd/E23104_01/download_readme.htm for details about compatible products and install types.
Level: 1

Type: ERROR

Impact: Installation

INST-07549: No compatible installation type found.

Cause: Incompatible Installation Type : {0}

Action: Incompatibility Details : {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07550: Unable to find dependent featuresets for the selected installation type

Cause: Unable to find dependent featuresets for the selected installation type. {0}

Action: Select a different install type or provide a different Oracle Home having all dependencies. Check http://docs.oracle.com/cd/E23104_01/download_readme.htm for details about compatible products and install types.
Level: 1

Type: ERROR

Impact: Installation

INST-07551: Unable to find dependent featuresets for the selected installation type

Cause: Not all depenedent featuresets for install type "{0}" could be found. {1}

Action: Select a different Oracle Home having all dependencies. Check http://docs.oracle.com/cd/E23104_01/download_readme.htm for details about compatible products and install types.
Level: 1

Type: ERROR

Impact: Installation

INST-07939: Error in validating install types

Cause: Unexpected error in validating install types

Action: Make sure entered values are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07940: Error in validating install types

Cause: This installation type cannot be installed, because the selected Oracle home contains Oracle Fusion Middleware Infrastructure.

Action: For more information about the prerequisites for this install type, see Installing and Configuring Oracle HTTP Server in the Oracle Fusion Middleware documentation library.
Level: 1

Type: ERROR

Impact: Installation

INST-07941: Error in validating install types

Cause: This installation type cannot be installed, because Oracle Fusion Middleware Infrastructure is not installed in the selected Oracle home.

Action: For more information about the prerequisites for this install type, see Installing and Configuring Oracle HTTP Server in the Oracle Fusion Middleware documentation library.
Level: 1

Type: ERROR

Impact: Installation

INST-08001: Validation of Middleware home location failed. Directory path invalid

Cause: Validation of Middleware home location failed. The location specified contains missing, mandatory directories

Action: Make sure that Oracle/Middleware is in the path
Level: 1

Type: ERROR

Impact: Installation

INST-08002: SSO Registration Failed.

Cause: IP Adress of this machine cannot be obtained.

Action: Check the network configuration of this machine
Level: 1

Type: ERROR

Impact: Installation

INST-08003: Internal Error: SSO Registration Failed.

Cause: There was an error while modifying the Oracle HTTP Server's configuration file.

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08004: Internal Error: Installation of Oracle Web Cache failed.

Cause: An unexpected error occurred while trying to create Web Cache component

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08005: Internal Error: Installation of Oracle HTTP Server failed.

Cause: An unexpected error occurred while trying to create Oracle HTTP Server component.

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08006: Internal Error: Starting OPMN failed.

Cause: An exception occurred while trying to start OPMN

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08007: Internal Error: Reload OPMN failed.

Cause: An exception occurred while trying to reload OPMN.

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08008: Internal Error: Creation of ReportsServer Component failed.

Cause: An exception occurred while creating the ReportsServer Component

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08009: Internal Error: Creation of ReportsTools Component failed.

Cause: An exception occurred while creating the ReportsTools Component

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08010: An error occurred while registering the schema: {0} with the WebLogic Server.

Cause: Registering Schema failed with the exception: {0}

Action: Check if the Database: {0} is up and running.
Level: 1

Type: ERROR

Impact: Installation

INST-08011: Internal Error: Creation of Forms System Component failed.

Cause: An exception occurred while creating the Forms System Component

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08012: Internal Error: Creation of FRSystemComponent failed.

Cause: An exception occurred while creating the FRSystemComponent

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08013: Internal Error: Creation of Discoverer System Component failed.

Cause: An exception occurred while creating the Discoverer System Component

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-10001: Error in validating Component Dependency Details

Cause: Dependency for {0} is missing. Missing dependent component ids are {1}.

Action: Make sure to select / specify all dependent components
Level: 1

Type: ERROR

Impact: Installation

INST-10002: Error in validating Component Dependency Details

Cause: Component Ids {0} are invalid

Action: Provide valid component id
Level: 1

Type: ERROR

Impact: Installation

INST-10003: Error in validating Component Dependency Details

Cause: An unexpected error occurred while validating Component Dependency Details

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-10101: Error in validating {0} Base Image Location

Cause: {0} Base Image Location is null or blank.

Action: Provide a valid {0} Base Image Location
Level: 1

Type: ERROR

Impact: Installation

INST-10102: Error in validating {0} Base Image Location

Cause: The {0} Base Image Location provided is not existing or not a valid file

Action: Provide a valid {0} Base Image Location
Level: 1

Type: ERROR

Impact: Installation

INST-10103: Error in validating the {0} Base Image Location for Assembly Builder

Cause: An unexpected error occurred while validating the {0} Base Image Location for Assembly Builder

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-10104: Error in validating {0} Base Image Location

Cause: The {0} Base Image File name must be {1}

Action: Provide a valid {0} Base Image Location
Level: 1

Type: ERROR

Impact: Installation

INST-10105: Error in validating {0} Base Image Virtual Machine configuration file Location

Cause: The {0} Base Image Virtual Machine configuration File (vm.cfg) is not existing

Action: The vm.cfg file must be present in same directory as the Base Image ({1}), provide a valid {0} Base Image Location
Level: 1

Type: ERROR

Impact: Installation

INST-10106: Error in validating Keystore

Cause: An unexpected error occurred while validating the {0} Keystore for Assembly Builder

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-10107: The Keystore path must not be null or blank

Cause: The Keystore path must not be null or blank

Action: Provide a valid Keystore path
Level: 1

Type: ERROR

Impact: Installation

INST-10108: The Keystore password must not be null or blank

Cause: The Keystore password must not be null or blank

Action: Provide a valid Keystore password
Level: 1

Type: ERROR

Impact: Installation

INST-10109: Invalid keystore.

Cause: Failed to validate the Keystore.

Action: Provide a valid Keystore
Level: 1

Type: ERROR

Impact: Installation

INST-10110: The Key password must not be null or blank

Cause: The Key password must not be null or blank

Action: Provide a valid Key password
Level: 1

Type: ERROR

Impact: Installation

INST-10111: The Key alias must not be null or blank

Cause: The Key alias must not be null or blank

Action: Provide a valid Key alias
Level: 1

Type: ERROR

Impact: Installation

INST-10112: Invalid key alias

Cause: Invalid key alias and password combination.

Action: Provide a valid Key alias and password combination
Level: 1

Type: ERROR

Impact: Installation

INST-10113: Error in validating Component Version

Cause: Component Version is null or blank.

Action: Provide a valid Component Version.
Level: 1

Type: ERROR

Impact: Installation

INST-10114: Error in validating Component List

Cause: Component List is null or blank.

Action: Provide a valid Component List.
Level: 1

Type: ERROR

Impact: Installation

INST-10115: Error in validating Oracle Home

Cause: Oracle Home is null or blank.

Action: Provide a valid Oracle Home.
Level: 1

Type: ERROR

Impact: Installation

INST-10116: Installation of Studio and Deployer detected in the selected Oracle Home. Installing into an existing Oracle Home is done to either reinstall binaries or to upgrade an Oracle Home from one release to another

Cause: Installation of Studio and Deployer detected in the selected Oracle Home.

Action: Installing into an existing Oracle Home is done to either reinstall binaries or to upgrade an Oracle Home from one release to another.
Level: 1

Type: ERROR

Impact: Installation

INST-10117: Error in validating the installed component in {0} Oracle Home

Cause: An unexpected error occurred while validating the installed component in {0} Oracle Home

Action: An unexpected error occurred while validating the installed component in {0} Oracle Home
Level: 1

Type: ERROR

Impact: Installation

13 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

14 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

15 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

16 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

17 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

18 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

19 MODPLSQL-00001 to MODPLSQL-00868

MODPLSQL-00001: mod_plsql: Out of memory

Cause: System has run out of memory

Action: Reduce memory usage in the system
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00010: mod_plsql: Out of memory

Cause: System has run out of memory

Action: Reduce memory usage in the system
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00102: mod_plsql: Wrong language, territory or charset in NLS_LANG value

Cause: Incorrect NLS_LANG value specified

Action: Refer to RDBMS and NLS documentation for the acceptable NLS_LANG value
Level: 1

Type: ALERT

Impact: Configuration

MODPLSQL-00350: mod_plsql: Bad Procedure/Argument name in the request

Cause: The procedure name and/or the argument is not a legal PL/SQL identifier

Action: Correct the procedure name and the arguments to be legal PL/SQL identifiers
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00367: mod_plsql: Illegal PLSQL identifer in input

Cause: The procedure name and/or the argument is not a legal PL/SQL identifier

Action: Correct the procedure name and the arguments to be legal PL/SQL identifiers
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00368: mod_plsql: No target procedure specified for invocation

Cause: The procedure name to invoke is not specified in the URL

Action: Specify a legal PL/SQL procedure to invoke
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00369: mod_plsql: Illegal procedure name, part exceeds 32 bytes

Cause: The procedure name specified exceeds the legal PLSQL identifier length

Action: Correct the procedure name to be a legal PL/SQL identifier
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00370: mod_plsql: Illegal procedure name, has an empty part

Cause: The procedure name is not a legal PLSQL identifier

Action: Correct the procedure name to be a legal PL/SQL identifier
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00371: mod_plsql: Illegal procedure name, too many parts

Cause: The procedure name is not a legal PLSQL identifier

Action: Correct the procedure name to be a legal PL/SQL identifier
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00868: mod_plsql: Failed to validate configuration parameters

Cause: Illegal configuration property specified in the mod_plsql configuration

Action: Refer to the logs for more details, and correct the offending configuration property
Level: 1

Type: ERROR

Impact: Configuration

20 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: 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-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-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-112902: Failed to close a resource. Error: %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-112903: Failed to open a resource file %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-112904: Parameter '%s' does not have a valid value to be decoded, received '%s'

Cause:

Action:
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: 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-112910: The OVAB Deployer config MXBean

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-112911: Set the web server url in the OVAB deployer

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-112912: Retrieve the web server url from OVAB depoyer

Cause:

Action:
Level: 1

Type: NOTIFICATION

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-112913: Cannot initialize 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-112914: Fail to register 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-112915: Fail to unregister the Ovab Deployer MBean {0}

Cause:

Action:
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

21 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-01650: -AGENT_URL=<agent_url> is a mandatory parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01651: Error while executing:

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-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-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-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-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-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-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-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-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-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-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-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-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-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

22 OHS-03501 to OHS-03813

OHS-03501: File copy failed because of {0} exception.

Cause:

Action: Check OHS Component provisioning files.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03502: {0} exception occurred while removing configuration files.

Cause:

Action: Check configuration files.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03503: {0} exception occurred while creating component.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03504: {0} exception occurred while registering the OHS content dir with BR Service.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03505: List KeyStore exception

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03506: OHS audit configuration load failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03507: OHS audit configuration save failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03508: Unable to set Custom Log configuration

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03509: CustomLog configuration is wrong

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03510: Exception while disabling OHS module

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03511: {0} exception occurred while trying to get configuration from configService.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03512: Configuration document not found.

Cause:

Action: Check for configuration document.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03513: {0} exception occured while trying to read document.

Cause:

Action: See exception to identify problem or check document.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03514: {0} exception occured while trying to write document.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03515: {0} exception occured while trying to read config segment.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03516: Null parameter(s) passed.

Cause:

Action: Pass non-null parameters.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03517: {0} exception occured while parsing directive.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03518: {0} exception occured while attempting to read httpd.conf.

Cause:

Action: See exception to identify problem or check the httpd.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03519: {0} exception occured while attempting to write httpd.conf.

Cause:

Action: See exception to identify problem or check the httpd.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03520: Nothing to save.

Cause:

Action: Create or load a file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03521: {0} exception occured while attempting to write mod_osso.conf.

Cause:

Action: See exception to identify problem or check the mod_osso.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03522: VirtualServer {0} does not exist

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03523: {0} exception occured while attempting to write mod_oc4j.conf.

Cause:

Action: See exception to identify problem or check the mod_oc4j.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03524: Can not find IfModule mod_oc4j.c container in mod_oc4j.conf

Cause:

Action: Check the mod_oc4j.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03525: mod_oc4j.conf file not present

Cause:

Action: Check for the mod_oc4j.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03526: Failed to read file {0}, because of {1} exception.

Cause:

Action: Check file path or directory location.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03527: Failed to write file {0}, because of {1} exception.

Cause:

Action: Check file path or directory location.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03528: Can not find value for directive {0}.

Cause:

Action: Check file for directive if it is actually required.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03529: httpd.conf has not been loaded.

Cause:

Action: Check the httpd.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03530: failed to delete directive

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03531: Object passed in is of an invalid class.

Cause:

Action: Pass an object of a valid class.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03532: mod_osso.conf has not been loaded.

Cause:

Action: Check the mod_osso.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03533: mod_oc4j.conf has not been loaded.

Cause:

Action: Check the mod_oc4j.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03534: Exception in getPropertiesFromBinaryFile: {0}

Cause:

Action: Check that the file has been created correctly.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03535: 902 format is not supported. Exception is {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03536: 902 format supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03537: Exception occured while obfuscating string contents. Exception is {0}.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03538: Exception occured while writing to osso.conf file. Exception is {0}.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03539: Exception in getOSSOConfFile: {0}

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03540: Error reading configuration document: {0}

Cause:

Action: Check that the location of the document has been correctly specified.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03541: Input parameters are null.

Cause:

Action: Provide appropriate arguments when calling mod_osso registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03542: SSO DB partner version received is null.

Cause:

Action: Check that SSO DB version is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03543: Partner application site ID received is null.

Cause:

Action: Check that partner site ID is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03544: Partner application site token received is null.

Cause:

Action: Check that partner site token is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03545: Partner application login URL received is null.

Cause:

Action: Check that login URL is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03546: Partner application logout URL received is null.

Cause:

Action: Check that logout URL is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03547: Partner application timeout cookie received is null.

Cause:

Action: Check that timeout cookie is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03548: Partner application timeout key received is null.

Cause:

Action: Check that timeout key is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03549: Partner application urlc version received is null.

Cause:

Action: Check that urlc version is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03550: Partner application preencryption mask received is null.

Cause:

Action: Check that preencryption mask is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03551: Partner application post-encryption mask received is null.

Cause:

Action: Check that post-encryption mask is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03552: Partner application cancel URL received is null.

Cause:

Action: Check that cancel URL is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03553: Partner application non-SSL SSO host received is null.

Cause:

Action: Check that non-SSL SSO host is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03554: Partner application OSSO configuration file path received is null.

Cause:

Action: Check that configuration file path is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03555: Exception occured during reading of input values. Error was: {0}

Cause:

Action: Check that all necessary inputs are correctly supplied to the partner registration tool.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03556: The osso.conf file was added successfully.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03557: Status: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03558: The osso.conf file was not added. Operation failed.

Cause:

Action: Check previous exception for additional information.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03559: The osso.conf file was retrieved successfully.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03560: The osso.conf file could not be retrieved. Operation failed.

Cause:

Action: Check previous exception for additional information.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03561: The osso.conf file was deleted successfully.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03562: The osso.conf file could not be deleted. Operation failed.

Cause:

Action: Check previous exception for additional information.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03563: Already enabled. Configuration document already exists.

Cause:

Action: Check name or select a diffent module.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03564: Null MAS configuration object encountered.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03565: ManagementException occurred reading {0}.

Cause:

Action: Check previous exception for additional information.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03566: IOException occurred reading {0}.

Cause:

Action: Check previous exception for additional information.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03567: failed to update file {0}.

Cause:

Action: Check previous exception for additional information.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03568: failed to update file due to invalid contents.

Cause:

Action: Check previous exception for additional information.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03569: Null exception reference encountered when attempting handling exception.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03570: ThreadLimit may not exceed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03571: ServerLimit may not exceed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03572: Max Clients exceeds range, raise ServerLimit.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03573: Max Clients exceeds range, raise ServerLimit or ThreadPerChild.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03574: mod_osso is not enabled. mod_osso must be enabled before modifying osso related directives.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03575: The value of ThreadLimit cannot be less than the value of ThreadsPerChild.

Cause:

Action: Use a larger value for ThreadLimit or lower the ThreadsPerChild value.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03576: The value of ThreadsPerChild cannot be greater than the value of ThreadLimit.

Cause:

Action: Use a smaller value for ThreadsPerChild or raise the value of ThreadLimit.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03577: The value of ServerLimit cannot be less than the value of MaxClients.

Cause:

Action: Use a larger value for ServerLimit or lower the value of MaxClients.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03578: The value of ServerLimit * ThreadsPerChild cannot be less than the value of MaxClients.

Cause:

Action: Use a larger value for ServerLimit and/or ThreadsPerChild, or lower the value of MaxClients.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03579: Virtual Host Already Exists

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03580: Not a proper Virtual Host Name

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03581: Enable Module failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03582: Module is not installed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03583: Register child MBean api failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03584: Proxy Port MBean registration failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03585: Audit MBean registartion failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03586: Parsing error while loading MBeans

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03587: Exception occurred while loading MBeans

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03588: Virtual Host creation failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03589: Duplicate virtual host found

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03590: Base Virtual host creation failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03591: Configuration file parsing failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03592: OraDev config MBean registration failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03593: Unregister of Keystore MBean success

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03594: Unregister of configuration MBeans failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03595: Unable to get VH objects from root OHS MBean

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03596: Load wallets failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03597: Removal of Virtual Host failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03598: Removal of Listen failed while removing VH

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03599: Configuration Restore failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03600: Configuration validation failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03601: Load failed with IOException

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03602: Module Name is wrong

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03603: Unable to find the MPM Name, Setting it to default Worker

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03604: Unable to find Server Name, Setting it to default AdminServer

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03701: Error log configuration not valid

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03702: Saving wallet is null

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03703: P12 Wallet is null; Possibly because the wallet is absent/not configured.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03704: CWallet is null, not able to load cwallet

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03705: Directive does not exist

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03706: WLPort not configured; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03707: WLHost not configured; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03708: WLCluster not configured; Not allowed to call listWLCluster

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03709: DynamicServerList is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03710: CertValidationPath is not configured

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03711: CertValidation is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03712: SSLWallet is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03713: SSLAuthtype is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03714: SSLCiphers is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03715: SSLVersions is not configured

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03716: SSLEnabled is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03801: Load Operation failed in VH SSLResource

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03802: Load Operation finished in VH SSLResource

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03803: Configuration file backup success

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03804: Load operation success

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03805: Module is already configured

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03806: Unregistered all configuration MBeans

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03807: Wildcard char, allow processing

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03808: Error log configuration mode is not apache

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03809: Error log Mode is apache

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03810: Listen Directive not configured

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03811: Listen Directive already exist for specified port

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03812: Configuration Restore success

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03813: OHS Validation successfull

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

23 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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-25037: Error while retrieving configuration property: {0}.

Cause: Unable to read from the messaging server configuration file 'configuration/appconfig.xml' or the named property does not exist.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25037: Error while retrieving configuration property: {0}.

Cause: Unable to read from the messaging server configuration file 'configuration/appconfig.xml' or the named property does not exist.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25038: Error while loading the messaging server configuration properties. Falling back to default configuration.

Cause: Unable to read from the messaging server configuration file 'configuration/appconfig.xml'.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25038: Error while loading the messaging server configuration properties. Falling back to default configuration.

Cause: Unable to read from the messaging server configuration file 'configuration/appconfig.xml'.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-25088: Unable to refresh the driver locator cache, due to the following error: {0}

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-25088: Unable to refresh the driver locator cache, due to the following error: {0}

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-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-25105: Initializing Messaging Store in {0} mode.

Cause: Initializing Messaging Store in persistent mode. Message history will persist across server restarts.

Action: n/a
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25105: Initializing Messaging Store in {0} mode.

Cause: Initializing Messaging Store in persistent mode. Message history will persist across server restarts.

Action: n/a
Level: 1

Type: NOTIFICATION

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-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-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-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-25110: An error occurred while initializing persistence session, with the following error message: {0}

Cause: An error occurred while attempting to initialize and log in to the TopLink persistence session.

Action: Check the reported error message and correct any configuration or database availability problems.
Level: 1

Type: WARNING

Impact: Process

SDP-25110: An error occurred while initializing persistence session, with the following error message: {0}

Cause: An error occurred while attempting to initialize and log in to the TopLink persistence session.

Action: Check the reported error message and correct any configuration or database availability problems.
Level: 1

Type: WARNING

Impact: Process

SDP-25201: No endpoint URL is available for the web service callback operation.

Cause: No endpoint URL is available for the web service listener callback.

Action: Ensure a valid callback URL is specified when registering a message or status listener.
Level: 1

Type: WARNING

Impact: Process

SDP-25201: No endpoint URL is available for the web service callback operation.

Cause: No endpoint URL is available for the web service listener callback.

Action: Ensure a valid callback URL is specified when registering a message or status listener.
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-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-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-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-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-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-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-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-25258: Error initializing the Servlet Endpoint Context. Parlay X module will not be able to service requests correctly.

Cause: Could not initialize the Servlet Endpoint Context.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25258: Error initializing the Servlet Endpoint Context. Parlay X module will not be able to service requests correctly.

Cause: Could not initialize the Servlet Endpoint Context.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25259: Error initializing access to Messaging Server. Parlay X module will not be able to service requests correctly.

Cause: Could not initialize internal Messaging Client endpoint.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25259: Error initializing access to Messaging Server. Parlay X module will not be able to service requests correctly.

Cause: Could not initialize internal Messaging Client endpoint.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

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-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-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-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-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-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-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-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-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-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-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-25310: The URL is malformed: {0}

Cause: The URL is malformed.

Action: The URL must be in file://path/filename format.
Level: 1

Type: ERROR

Impact: Process

SDP-25310: The URL is malformed: {0}

Cause: The URL is malformed.

Action: The URL must be in 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-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-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-25313: Null Pointer Exception was caught.

Cause: Null Pointer Exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25313: Null Pointer Exception was caught.

Cause: Null Pointer 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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-25332: Directory for User Preferences Services File Persistence does not exist.

Cause: Directory for User Preferences Services File Persistence does not exist.

Action: System will try to create the directory.
Level: 1

Type: WARNING

Impact: Process

SDP-25332: Directory for User Preferences Services File Persistence does not exist.

Cause: Directory for User Preferences Services File Persistence does not exist.

Action: System will try to create the directory.
Level: 1

Type: WARNING

Impact: Process

SDP-25333: Invalid directory: {0}

Cause: The given path was not a valid directory.

Action: Specify a valid directory, not a file.
Level: 1

Type: WARNING

Impact: Process

SDP-25333: Invalid directory: {0}

Cause: The given path was not a valid directory.

Action: Specify a valid directory, not a file.
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-25334: Device name is null.

Cause: Device name is null.

Action: Provide a valid Device name.
Level: 1

Type: ERROR

Impact: Process

SDP-25335: invalid user ID: {0}

Cause: An invalid user ID was specified.

Action: Specify a valid user ID.
Level: 1

Type: WARNING

Impact: Process

SDP-25335: invalid user ID: {0}

Cause: An invalid user ID was specified.

Action: Specify a valid user ID.
Level: 1

Type: WARNING

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-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-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-25338: Cannot find object to update: {0}

Cause: Cannot find object to update.

Action: Could be a problem in implementing persistence.
Level: 1

Type: ERROR

Impact: Process

SDP-25338: Cannot find object to update: {0}

Cause: Cannot find object to update.

Action: Could be a problem in implementing persistence.
Level: 1

Type: ERROR

Impact: Process

SDP-25339: Object already exists.

Cause: Tried to persist an object that already exists.

Action: To overwrite existing value, use '-overwrite' flag.
Level: 1

Type: ERROR

Impact: Process

SDP-25339: Object already exists.

Cause: Tried to persist an object that already exists.

Action: To overwrite existing value, use '-overwrite' flag.
Level: 1

Type: ERROR

Impact: Process

SDP-25340: Object not found.

Cause: Tried to remove an object that does not exist.

Action: (None)
Level: 1

Type: ERROR

Impact: Process

SDP-25340: Object not found.

Cause: Tried to remove an object that does not exist.

Action: (None)
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-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-25342: Cannot find default address for user {0}.

Cause: The default address of that user was not set.

Action: Check that default address is set from UserPreference Administrator page.
Level: 1

Type: ERROR

Impact: Process

SDP-25342: Cannot find default address for user {0}.

Cause: The default address of that user was not set.

Action: Check that default address is set from UserPreference Administrator page.
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-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-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-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-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-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-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-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-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-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-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-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-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-25355: Error while loading the business rule terms configuration

Cause: The business rule terms configuration file configuration/businessterms.xml could not be read.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25355: Error while loading the business rule terms configuration

Cause: The business rule terms configuration file configuration/businessterms.xml could not be read.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

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-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-25357: Cannot persist rule set for user GUID {0}, because one already exists.

Cause: A rule set already exists for this user.

Action: Remove the conflicting rule set, or overwrite it.
Level: 1

Type: ERROR

Impact: Process

SDP-25357: Cannot persist rule set for user GUID {0}, because one already exists.

Cause: A rule set already exists for this user.

Action: Remove the conflicting rule set, or overwrite it.
Level: 1

Type: ERROR

Impact: Process

SDP-25358: Cannot upload rule set for user GUID {0}, because one already exists.

Cause: A rule set already exists for this user.

Action: Try uploading the user messaging preferences using merge option 'overwrite' or 'append' (refer to command help for details).
Level: 1

Type: ERROR

Impact: Process

SDP-25358: Cannot upload rule set for user GUID {0}, because one already exists.

Cause: A rule set already exists for this user.

Action: Try uploading the user messaging preferences using merge option 'overwrite' or 'append' (refer to command help for details).
Level: 1

Type: ERROR

Impact: Process

SDP-25359: Cannot upload user device for user GUID {0}, because one already exists.

Cause: A user device already exists for this user.

Action: Try uploading the user messaging preferences using merge option 'overwrite' or 'append' (refer to command help for details).
Level: 1

Type: ERROR

Impact: Process

SDP-25359: Cannot upload user device for user GUID {0}, because one already exists.

Cause: A user device already exists for this user.

Action: Try uploading the user messaging preferences using merge option 'overwrite' or 'append' (refer to command help for details).
Level: 1

Type: ERROR

Impact: Process

SDP-25360: Initializing User Messaging Preferences services.

Cause: User Messaging Preferences services were initialized as part of application startup or deployment.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25360: Initializing User Messaging Preferences services.

Cause: User Messaging Preferences services were initialized as part of application startup or deployment.

Action: None.
Level: 1

Type: NOTIFICATION

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-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-25362: This User Preference object cannot be deleted because it is backed by the user profile in the identity store: {0}.

Cause: An attempt was made to delete a read-only object backed by the user profile in the identity store.

Action: None.
Level: 1

Type: ERROR

Impact: Process

SDP-25362: This User Preference object cannot be deleted because it is backed by the user profile in the identity store: {0}.

Cause: An attempt was made to delete a read-only object backed by the user profile in the identity store.

Action: None.
Level: 1

Type: ERROR

Impact: Process

SDP-25363: No UserRuleSet exists for userID {0}.

Cause: The user does not have a UserRuleSet.

Action: Check spelling of user ID.
Level: 1

Type: ERROR

Impact: Process

SDP-25363: No UserRuleSet exists for userID {0}.

Cause: The user does not have a UserRuleSet.

Action: Check spelling of user ID.
Level: 1

Type: ERROR

Impact: Process

SDP-25364: setFilterOperation has not been called.

Cause: Incorrect calling sequence.

Action: Invoke method setFilterOperation() first.
Level: 1

Type: ERROR

Impact: Process

SDP-25364: setFilterOperation has not been called.

Cause: Incorrect calling sequence.

Action: Invoke method setFilterOperation() first.
Level: 1

Type: ERROR

Impact: Process

SDP-25365: Condition does not exist: {0}

Cause: Condition cannot be found.

Action: Check spelling of condition name or ID.
Level: 1

Type: ERROR

Impact: Process

SDP-25365: Condition does not exist: {0}

Cause: Condition cannot be found.

Action: Check spelling of condition name or ID.
Level: 1

Type: ERROR

Impact: Process

SDP-25366: Source parameter is greater than the number of conditions.

Cause: Source parameter is out of range.

Action: Provide correct source parameter.
Level: 1

Type: ERROR

Impact: Process

SDP-25366: Source parameter is greater than the number of conditions.

Cause: Source parameter is out of range.

Action: Provide correct source parameter.
Level: 1

Type: ERROR

Impact: Process

SDP-25367: Error creating FilterCondition, type {0} is not valid.

Cause: Incorrect type has been found.

Action: Use correct type.
Level: 1

Type: ERROR

Impact: Process

SDP-25367: Error creating FilterCondition, type {0} is not valid.

Cause: Incorrect type has been found.

Action: Use correct type.
Level: 1

Type: ERROR

Impact: Process

SDP-25368: Term {0} is not valid.

Cause: Term is not valid.

Action: Use a valid term.
Level: 1

Type: ERROR

Impact: Process

SDP-25368: Term {0} is not valid.

Cause: Term is not valid.

Action: Use a valid term.
Level: 1

Type: ERROR

Impact: Process

SDP-25369: Term of type {0} does not accept operation {1}.

Cause: Unmatched type and operation.

Action: Use matching type and operation.
Level: 1

Type: ERROR

Impact: Process

SDP-25369: Term of type {0} does not accept operation {1}.

Cause: Unmatched type and operation.

Action: Use matching type and operation.
Level: 1

Type: ERROR

Impact: Process

SDP-25370: Method setFilterTerm() has not been called.

Cause: setFilterTerm() method has not been called prior to current method invocation.

Action: Invoke setFilterTerm() first.
Level: 1

Type: ERROR

Impact: Process

SDP-25370: Method setFilterTerm() has not been called.

Cause: setFilterTerm() method has not been called prior to current method invocation.

Action: Invoke setFilterTerm() first.
Level: 1

Type: ERROR

Impact: Process

SDP-25371: FilterTerm should be initialized.

Cause: FilterTerm has not been initialized.

Action: Initialize FilterTerm first.
Level: 1

Type: ERROR

Impact: Process

SDP-25371: FilterTerm should be initialized.

Cause: FilterTerm has not been initialized.

Action: Initialize FilterTerm first.
Level: 1

Type: ERROR

Impact: Process

SDP-25372: Inconsistent FilterTerm.getName() : {0}, {1}

Cause: Name of filter term does not match the name of filter condition.

Action: Fix the inconsistency of filter term name and filter condition name.
Level: 1

Type: ERROR

Impact: Process

SDP-25372: Inconsistent FilterTerm.getName() : {0}, {1}

Cause: Name of filter term does not match the name of filter condition.

Action: Fix the inconsistency of filter term name and filter condition name.
Level: 1

Type: ERROR

Impact: Process

SDP-25373: Inconsistent FilterTerm.getTypeName() : {0}, {1}

Cause: Type name of filter term does not match the name of filter condition.

Action: Fix the inconsistency of filter term type name and filter condition type name.
Level: 1

Type: ERROR

Impact: Process

SDP-25373: Inconsistent FilterTerm.getTypeName() : {0}, {1}

Cause: Type name of filter term does not match the name of filter condition.

Action: Fix the inconsistency of filter term type name and filter condition type name.
Level: 1

Type: ERROR

Impact: Process

SDP-25374: Term operation should be defined.

Cause: Undefined term operation.

Action: Define operation of the term.
Level: 1

Type: ERROR

Impact: Process

SDP-25374: Term operation should be defined.

Cause: Undefined term operation.

Action: Define operation of the term.
Level: 1

Type: ERROR

Impact: Process

SDP-25375: Term of type {0} does not accept operation {1}.

Cause: Operation was not accepted by the term.

Action: Specify an operation that can be accepted by the term.
Level: 1

Type: ERROR

Impact: Process

SDP-25375: Term of type {0} does not accept operation {1}.

Cause: Operation was not accepted by the term.

Action: Specify an operation that can be accepted by the term.
Level: 1

Type: ERROR

Impact: Process

SDP-25376: TermOperation must be set.

Cause: TermOperation was not set.

Action: Set TermOperation properly.
Level: 1

Type: ERROR

Impact: Process

SDP-25376: TermOperation must be set.

Cause: TermOperation was not set.

Action: Set TermOperation properly.
Level: 1

Type: ERROR

Impact: Process

SDP-25377: Operand {0} just allows {1} arguments, but {2} is given.

Cause: Number of arguments does not meet the requirement of the operand.

Action: Set correct number of arguments.
Level: 1

Type: ERROR

Impact: Process

SDP-25377: Operand {0} just allows {1} arguments, but {2} is given.

Cause: Number of arguments does not meet the requirement of the operand.

Action: Set correct number of arguments.
Level: 1

Type: ERROR

Impact: Process

SDP-25378: Object {0} should be of type {1}.

Cause: Object has an incorrect Java type.

Action: Correct the type of object.
Level: 1

Type: ERROR

Impact: Process

SDP-25378: Object {0} should be of type {1}.

Cause: Object has an incorrect Java type.

Action: Correct the type of object.
Level: 1

Type: ERROR

Impact: Process

SDP-25379: Type {0} is not supported.

Cause: Object's type is not supported by User Preferences.

Action: Change the type of object to one of following supported Java types: String, Integer, Double and Date
Level: 1

Type: ERROR

Impact: Process

SDP-25379: Type {0} is not supported.

Cause: Object's type is not supported by User Preferences.

Action: Change the type of object to one of following supported Java types: String, Integer, Double and Date
Level: 1

Type: ERROR

Impact: Process

SDP-25380: User {0} does not exist in the system.

Cause: User name not found.

Action: Provide the correct user name.
Level: 1

Type: ERROR

Impact: Process

SDP-25380: User {0} does not exist in the system.

Cause: User name not found.

Action: Provide the correct user name.
Level: 1

Type: ERROR

Impact: Process

SDP-25381: Device not found for user {0}.

Cause: Device does not exist.

Action: Provide a valid Device name or username.
Level: 1

Type: ERROR

Impact: Process

SDP-25381: Device not found for user {0}.

Cause: Device does not exist.

Action: Provide a valid Device name or username.
Level: 1

Type: ERROR

Impact: Process

SDP-25382: DeliveryType is missing in the address {0}.

Cause: Address does not have required DeliveryType.

Action: Provide a valid DeliveryType in the address in <DeliveryType>:<Address> format.
Level: 1

Type: ERROR

Impact: Process

SDP-25382: DeliveryType is missing in the address {0}.

Cause: Address does not have required DeliveryType.

Action: Provide a valid DeliveryType in the address in <DeliveryType>:<Address> format.
Level: 1

Type: ERROR

Impact: Process

SDP-25383: Cannot persist device address {0}.

Cause: An exception occurred when storing device address.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25383: Cannot persist device address {0}.

Cause: An exception occurred when storing device address.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25384: Cannot create RuleSet for the user {0}.

Cause: An exception occurred while creating RuleSet for this user.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25384: Cannot create RuleSet for the user {0}.

Cause: An exception occurred while creating RuleSet for this user.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25385: Saving UserRuleSet failed. Cannot get XMLString for user {0}.

Cause: An exception occurred while savinging RuleSet for this user.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25385: Saving UserRuleSet failed. Cannot get XMLString for user {0}.

Cause: An exception occurred while savinging RuleSet for this user.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25386: Could not find entity to update.

Cause: Unable to find the entity in storage.

Action: None.
Level: 1

Type: ERROR

Impact: Process

SDP-25386: Could not find entity to update.

Cause: Unable to find the entity in storage.

Action: None.
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-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-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-25389: Error while loading profiles.xml

Cause: The configuration file configuration/profiles.xml could not be read.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25389: Error while loading profiles.xml

Cause: The configuration file configuration/profiles.xml could not be read.

Action: Check the stack trace for more details.
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-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-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-25401: Unable to set the parameter {0} in the configuration because of exception {1}.

Cause: An exception has occurred while attempting to set the specified parameter in the configuration object.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25401: Unable to set the parameter {0} in the configuration because of exception {1}.

Cause: An exception has occurred while attempting to set the specified parameter in the configuration object.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25402: Could not find the value for the configuration parameter {0}, using default value.

Cause: There is no such entry for the parameter {0} in the configuration file.

Action: Check configuration parameter.
Level: 1

Type: ERROR

Impact: Process

SDP-25402: Could not find the value for the configuration parameter {0}, using default value.

Cause: There is no such entry for the parameter {0} in the configuration file.

Action: Check configuration parameter.
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-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-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-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-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-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-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-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-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-25411: Unable to load Driver properties.

Cause: An exception has occurred while attempting to load the driver configuration properties.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25411: Unable to load Driver properties.

Cause: An exception has occurred while attempting to load the driver configuration properties.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25413: Could not find the value for the configuration parameter {0}, using default value.

Cause: There is no such entry for the parameter {0} in the configuration file.

Action: Check configuration parameter.
Level: 1

Type: WARNING

Impact: Process

SDP-25413: Could not find the value for the configuration parameter {0}, using default value.

Cause: There is no such entry for the parameter {0} in the configuration file.

Action: Check configuration parameter.
Level: 1

Type: WARNING

Impact: Process

SDP-25414: Could not find the application deployment MBean for {0}

Cause: The application may not have started correctly.

Action: Check the application deployment status.
Level: 1

Type: WARNING

Impact: Process

SDP-25414: Could not find the application deployment MBean for {0}

Cause: The application may not have started correctly.

Action: Check the application deployment status.
Level: 1

Type: WARNING

Impact: Process

SDP-25415: Found multiple application deployment MBeans for {0}

Cause: The application may not have started correctly.

Action: Check the application deployment status.
Level: 1

Type: WARNING

Impact: Process

SDP-25415: Found multiple application deployment MBeans for {0}

Cause: The application may not have started correctly.

Action: Check the application deployment status.
Level: 1

Type: WARNING

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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-25519: QueueWorker rejected

Cause: QueueWorker rejected

Action: Check WorkManager configuration.
Level: 1

Type: ERROR

Impact: Process

SDP-25520: MessagingWebServiceClientImpl.send() operation failed.

Cause: An exception has occurred when invoking webservice send().

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25520: MessagingWebServiceClientImpl.send() operation failed.

Cause: An exception has occurred when invoking webservice send().

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25521: MessagingWebServiceClientImpl.receive() operation failed.

Cause: An exception has occurred while receiving messages from webservice.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25521: MessagingWebServiceClientImpl.receive() operation failed.

Cause: An exception has occurred while receiving messages from webservice.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25522: The application onMessage() callback operation failed.

Cause: An exception has occurred while attempting to call the application onMessage callback method.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25522: The application onMessage() callback operation failed.

Cause: An exception has occurred while attempting to call the application onMessage callback method.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25523: The application onStatus() callback operation failed.

Cause: An exception has occurred while attempting to call the application onStatus callback method.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25523: The application onStatus() callback operation failed.

Cause: An exception has occurred while attempting to call the application onStatus callback method.

Action: Check the stack trace for more details.
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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-25714: Access control exception was caught. Name: {0} Action:{1}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25714: Access control exception was caught. Name: {0} Action:{1}.

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-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-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-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-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-25719: Failed to authenticate user {0}.

Cause: Failed to authenticate a user.

Action: Check username and password and try again.
Level: 1

Type: ERROR

Impact: Process

SDP-25719: Failed to authenticate user {0}.

Cause: Failed to authenticate a user.

Action: Check username and password and try again.
Level: 1

Type: ERROR

Impact: Process

SDP-25720: Sender Address is null or empty.

Cause: Sender Address has an error.

Action: Enter a valid non-null value for sender.
Level: 1

Type: ERROR

Impact: Process

SDP-25720: Sender Address is null or empty.

Cause: Sender Address has an error.

Action: Enter a valid non-null value for sender.
Level: 1

Type: ERROR

Impact: Process

SDP-25721: Recipient Address is null or empty.

Cause: Recipient Address has an error.

Action: Enter a valid non-null value for Recipient.
Level: 1

Type: ERROR

Impact: Process

SDP-25721: Recipient Address is null or empty.

Cause: Recipient Address has an error.

Action: Enter a valid non-null value for Recipient.
Level: 1

Type: ERROR

Impact: Process

SDP-25722: Message content is empty.

Cause: Message content was not set properly.

Action: Enter a valid non-null value for the content.
Level: 1

Type: ERROR

Impact: Process

SDP-25722: Message content is empty.

Cause: Message content was not set properly.

Action: Enter a valid non-null value for the content.
Level: 1

Type: ERROR

Impact: Process

SDP-25723: Message object is null.

Cause: Message is null.

Action: Set a valid non-null value of Message object.
Level: 1

Type: ERROR

Impact: Process

SDP-25723: Message object is null.

Cause: Message is null.

Action: Set a valid non-null value of Message object.
Level: 1

Type: ERROR

Impact: Process

SDP-25724: Message subject and content are null.

Cause: Message subject and content.

Action: Enter a valid non-null value for subject and/or content.
Level: 1

Type: ERROR

Impact: Process

SDP-25724: Message subject and content are null.

Cause: Message subject and content.

Action: Enter a valid non-null value for subject and/or content.
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-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-25726: Connection failed to remote host {0} using HTTP Proxy {1}. Error: {2}.

Cause: There was a problem with either the remote host or the HTTP Proxy. Check the associated connection error for the exact cause.

Action: Check the value of the remote host and the HTTP Proxy settings.
Level: 1

Type: ERROR

Impact: Process

SDP-25726: Connection failed to remote host {0} using HTTP Proxy {1}. Error: {2}.

Cause: There was a problem with either the remote host or the HTTP Proxy. Check the associated connection error for the exact cause.

Action: Check the value of the remote host and the HTTP Proxy settings.
Level: 1

Type: ERROR

Impact: Process

SDP-25727: Unable to create JMS QueueSender, {0}. Cause: There was a problem in the connection to the JMS provider.

Cause: There was a problem in the connection to the JMS provider.

Action: Check the container log for additional errors from the JMS adapter.
Level: 1

Type: ERROR

Impact: Process

SDP-25727: Unable to create JMS QueueSender, {0}. Cause: There was a problem in the connection to the JMS provider.

Cause: There was a problem in the connection to the JMS provider.

Action: Check the container log for additional errors from the JMS adapter.
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-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-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-25730: QueueWorker got exception.

Cause: QueueWorker got exception.

Action: Check the log for related information.
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-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-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-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-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-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-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-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-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-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-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-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 driver configuration file at {0}.

Cause: Error occurred while deleting the old driver configuration file.

Action: Check the file system. Correct the problem before running the Upgrade Assistant again.
Level: 1

Type: 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-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-25850: Oracle User Messaging Service schema upgraded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

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-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-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-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-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.

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-25855: Error in upgrading Oracle User Messaging Service schema.

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-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-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-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-26002: The driver {0} is operational

Cause: The driver is operational

Action: None
Level: 1

Type: NOTIFICATION

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-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-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-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-26009: Could not get JNDI InitialContext.

Cause: None

Action: None
Level: 1

Type: ERROR

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-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().

Cause: Exception thrown while invoking registerDriverInfo().

Action: Check stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26011: Failed to invoke registerDriverInfo().

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-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 cleanly stop driver: {0}.

Cause: Unable to cleanly stop driver.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26013: Unable to cleanly stop driver: {0}.

Cause: Unable to cleanly 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-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-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-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-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-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-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-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}. Exception: {1}

Cause: Illegal DeliveryType specified.

Action: Check message delivery type.
Level: 1

Type: ERROR

Impact: Process

SDP-26022: Illegal DeliveryType specified, ignoring type {0}. Exception: {1}

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-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-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-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-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-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-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: Unable to load driver configuration properties from 'usermessagingconfig.xml'.

Cause: An exception occurred while attempting to load the driver configuration properties from 'usermessagingconfig.xml'.

Action: Check the stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-26029: Unable to load driver configuration properties from 'usermessagingconfig.xml'.

Cause: An exception occurred while attempting to load the driver configuration properties from 'usermessagingconfig.xml'.

Action: Check the stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-26030: Unable to schedule worker used to attempt driver registration.

Cause: An exception occurred while scheduling a worker to attempt driver registration.

Action: Check the stack trace.
Level: 1

Type: WARNING

Impact: Process

SDP-26030: Unable to schedule worker used to attempt driver registration.

Cause: An exception occurred while scheduling a worker to attempt driver registration.

Action: Check the stack trace.
Level: 1

Type: WARNING

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-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-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-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-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 with the following error message: {1}. 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-26035: JNDI lookup of server command endpoint {0} failed with the following error message: {1}. 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-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-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-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-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-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-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-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-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-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-26108: Failed to initialize e-mail driver

Cause: Could not initialize Email Driver.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all e-mail servers are up.
Level: 1

Type: ERROR

Impact: Process

SDP-26108: Failed to initialize e-mail driver

Cause: Could not initialize Email Driver.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all e-mail servers are up.
Level: 1

Type: ERROR

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-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-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-26111: Could not remove listener from Email Driver

Cause: Could not remove listener from Email Driver

Action: Check stack trace or error log
Level: 1

Type: ERROR

Impact: Process

SDP-26111: Could not remove listener from Email Driver

Cause: Could not remove listener from Email Driver

Action: Check stack trace or error log
Level: 1

Type: ERROR

Impact: Process

SDP-26112: Null protocol error

Cause: Protocol was null.

Action: Specify an appropriate protocol for this driver.
Level: 1

Type: ERROR

Impact: Process

SDP-26112: Null protocol error

Cause: Protocol was null.

Action: Specify an appropriate protocol for this driver.
Level: 1

Type: ERROR

Impact: Process

SDP-26113: No incoming e-mail server.

Cause: Incoming server was not set.

Action: Set incoming server parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-26113: No incoming e-mail server.

Cause: Incoming server was not set.

Action: Set incoming server parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-26114: Username is missing.

Cause: Username was not set.

Action: Set the username in e-mail driver parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-26114: Username is missing.

Cause: Username was not set.

Action: Set the username in e-mail driver parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-26115: Failed to receive an inbound e-mail message

Cause: An exception has occurred while receiving an inbound e-mail message.

Action: Check stack trace or error log.
Level: 1

Type: WARNING

Impact: Process

SDP-26115: Failed to receive an inbound e-mail message

Cause: An exception has occurred while receiving an inbound e-mail message.

Action: Check stack trace or error log.
Level: 1

Type: WARNING

Impact: Process

SDP-26116: Protocol {0} is not supported.

Cause: An unsupported protocol was provided.

Action: Check the e-mail protocol name in e-mail driver parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-26116: Protocol {0} is not supported.

Cause: An unsupported protocol was provided.

Action: Check the e-mail protocol name in e-mail driver parameters.
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-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-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-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-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-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-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}

Cause: Could not initialize Email Store for user.

Action: Check stack trace or error log. Check username and password.
Level: 1

Type: ERROR

Impact: Process

SDP-26123: Could not initialize Email Store for user {0}

Cause: Could not initialize Email Store for user.

Action: Check stack trace or error log. Check username and password.
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-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-26125: An exception has occurred while sending out a message.

Cause: An exception occurred while sending out a message.

Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.
Level: 1

Type: ERROR

Impact: Process

SDP-26125: An exception has occurred while sending out a message.

Cause: An exception occurred while sending out a message.

Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.
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-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-26127: Collision on e-mail message polling. Pausing for {0} seconds.

Cause: Multiple e-mail drivers polling the same e-mail account at the same time.

Action: (None)
Level: 1

Type: WARNING

Impact: Process

SDP-26127: Collision on e-mail message polling. Pausing for {0} seconds.

Cause: Multiple e-mail drivers polling the same e-mail account at the same time.

Action: (None)
Level: 1

Type: WARNING

Impact: Process

SDP-26128: A duplicate inbound e-mail message has been discarded: gateway message ID: {0}, recipient addresses: {1}, subject: {2}.

Cause: A duplicate message was detected and discarded by the e-mail receiver.

Action: (None)
Level: 1

Type: WARNING

Impact: Process

SDP-26128: A duplicate inbound e-mail message has been discarded: gateway message ID: {0}, recipient addresses: {1}, subject: {2}.

Cause: A duplicate message was detected and discarded by the e-mail receiver.

Action: (None)
Level: 1

Type: WARNING

Impact: Process

SDP-26129: Unable to deliver to following addresses: {0} Reason: {1}

Cause: Recipient e-mail address was valid but sending failed for reason indicated in error message.

Action: Ensure that e-mail driver and SMTP server are operational and configured correctly, baed on information provided in error message.
Level: 1

Type: WARNING

Impact: Process

SDP-26129: Unable to deliver to following addresses: {0} Reason: {1}

Cause: Recipient e-mail address was valid but sending failed for reason indicated in error message.

Action: Ensure that e-mail driver and SMTP server are operational and configured correctly, baed on information provided in error message.
Level: 1

Type: WARNING

Impact: Process

SDP-26130: 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-26130: 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-26131: 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-26131: 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-26132: No configuration was found for this Email Driver deployment: {0}. Create a configuration for {0}.

Cause: No configuration was found for this Email Driver deployment.

Action: Create a configuration this Email Driver.
Level: 1

Type: ERROR

Impact: Process

SDP-26132: No configuration was found for this Email 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-26133: Email Driver {0} is not configured with all the mandatory properties. Configure this driver.

Cause: Email Driver was not configured with all the mandatory properties.

Action: Configure this driver.
Level: 1

Type: ERROR

Impact: Process

SDP-26133: Email Driver {0} is not configured with inbound or outbound properties. Driver disabled until configured.

Cause: Email Driver was not configured for inbound or outbound traffic.

Action: Configure this driver.
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-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-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-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: Received status message with incorrect format.

Cause: The status received from SMSC does not have message ID or state.

Action: Correct the SMSC.
Level: 1

Type: ERROR

Impact: Process

SDP-26153: Received status message with incorrect format.

Cause: The status received from SMSC does not have message ID or state.

Action: Correct the SMSC.
Level: 1

Type: ERROR

Impact: Process

SDP-26154: Failed to process received status in SMPP driver, because driver context is null.

Cause: Driver Context is null

Action: Check driver context.
Level: 1

Type: ERROR

Impact: Process

SDP-26154: Failed to process received status in SMPP driver, because driver context is null.

Cause: Driver Context is null

Action: Check driver context.
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-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-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-26157: SMPP driver failed to send out a message, because Message object is null.

Cause: Null message object.

Action: Check the caller of this method.
Level: 1

Type: ERROR

Impact: Process

SDP-26157: SMPP driver failed to send out a message, because Message object is null.

Cause: Null message object.

Action: Check the caller of this method.
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-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-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: SMPP Driver not configured. Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.

Cause: SMPP Driver was not configured.

Action: Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.
Level: 1

Type: ERROR

Impact: Process

SDP-26160: SMPP Driver not configured. Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.

Cause: SMPP Driver was not configured.

Action: Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.
Level: 1

Type: ERROR

Impact: Process

SDP-26161: Starting SMPP Driver: {0}

Cause: SMPP Driver resource adapter initialization.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26161: Starting SMPP Driver: {0}

Cause: SMPP Driver resource adapter initialization.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26162: Message content could not be decoded using character set {0}

Cause: The message content retrieved from the SMSC could not be decoded using the specified character set.

Action: Ensure that the Default Encoding configuration parameter is correct.
Level: 1

Type: WARNING

Impact: Process

SDP-26162: Message content could not be decoded using character set {0}

Cause: The message content retrieved from the SMSC could not be decoded using the specified character set.

Action: Ensure that the Default Encoding configuration parameter is correct.
Level: 1

Type: WARNING

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-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-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-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-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-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-26201: Unable to remove listener from XMPPDriver.

Cause: Unable to remove listener from XMPPDriver .

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26201: Unable to remove listener from XMPPDriver.

Cause: Unable to remove listener from XMPPDriver .

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26202: Unable to shut down XMPPDriver.

Cause: Unable to shut down XMPPDriver.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26202: Unable to shut down XMPPDriver.

Cause: Unable to shut down XMPPDriver.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26203: XMPP Driver not configured. Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.

Cause: XMPP Driver was not configured.

Action: Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.
Level: 1

Type: ERROR

Impact: Process

SDP-26203: XMPP Driver not configured. Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.

Cause: XMPP Driver was not configured.

Action: Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.
Level: 1

Type: ERROR

Impact: Process

SDP-26204: Error occurred while initializing XMPPDriver {0}

Cause: Error occurred while initializing driver instance.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26204: Error occurred while initializing XMPPDriver {0}

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-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-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-26207: Invalid value for im.retry.limit. Value reset to default - {0}

Cause: Invalid value for im.retry.limit. Value reset to default

Action: Specify a valid value for im.retry.limit
Level: 1

Type: WARNING

Impact: Process

SDP-26207: Invalid value for im.retry.limit. Value reset to default - {0}

Cause: Invalid value for im.retry.limit. Value reset to default

Action: Specify a valid value for im.retry.limit
Level: 1

Type: WARNING

Impact: Process

SDP-26208: Invalid value for im.retry.interval. Value reset to default - {0} seconds

Cause: Invalid value for im.retry.interval. Value reset to default.

Action: Specify a valid value for im.retry.interval
Level: 1

Type: WARNING

Impact: Process

SDP-26208: Invalid value for im.retry.interval. Value reset to default - {0} seconds

Cause: Invalid value for im.retry.interval. Value reset to default.

Action: Specify a valid value for im.retry.interval
Level: 1

Type: WARNING

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-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-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-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-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-26215: The XMPP driver has no previous account to replace.

Cause: No previous XMPP (IM) account was found. Unable to replace previous account.

Action: None
Level: 1

Type: WARNING

Impact: Process

SDP-26215: The XMPP driver has no previous account to replace.

Cause: No previous XMPP (IM) account was found. Unable to replace previous account.

Action: None
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-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-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-26218: I/O problem using HTTP Proxy {0} for account: {1}

Cause: The connection with the HTTP Proxy was broken.

Action: Check stack trace for more information. Check HTTP Proxy settings to see if proxy is correct and reachable.
Level: 1

Type: ERROR

Impact: Process

SDP-26218: I/O problem using HTTP Proxy {0} for account: {1}

Cause: The connection with the HTTP Proxy was broken.

Action: Check stack trace for more information. Check HTTP Proxy settings to see if proxy is correct and reachable.
Level: 1

Type: ERROR

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-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-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-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-26222: Agent registration failed for {0}. Error Code: {1}

Cause: Agent registration failed.

Action: Check error code and from address.
Level: 1

Type: ERROR

Impact: Process

SDP-26222: Agent registration failed for {0}. Error Code: {1}

Cause: Agent registration failed.

Action: Check error code and from address.
Level: 1

Type: ERROR

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-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-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-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-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-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-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-26229: Plaintext authentication failed; disconnecting from server: {0}

Cause: Plaintext authentication failed.

Action: Check username and password and check with the Jabber/XMPP server administrator.
Level: 1

Type: ERROR

Impact: Process

SDP-26229: Plaintext authentication failed; disconnecting from server: {0}

Cause: Plaintext authentication failed.

Action: Check username and password and check with the Jabber/XMPP server administrator.
Level: 1

Type: ERROR

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-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-26231: Failed to login to Jabber/XMPP server: {0}

Cause: Failed to login to Jabber/XMPP server.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26231: Failed to login to Jabber/XMPP server: {0}

Cause: Failed to login to Jabber/XMPP server.

Action: Check the stack trace for more details.
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-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-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-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-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 {0} transport is not enabled in the driver. Set the value for driver parameter: {1}.

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-26238: Cannot deliver to this {0} user, because {0} transport is not enabled in the driver. Set the value for driver parameter: {1}.

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-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-26240: Max Retry Limit ( {0} ) is reached. Restart the driver to try reconnecting for account {1}.

Cause: The Max Retry Limit was reached while attempting to reconnect.

Action: Restart the XMPP driver to try again.
Level: 1

Type: ERROR

Impact: Process

SDP-26240: Max Retry Limit ( {0} ) is reached. Restart the driver to try reconnecting for account {1}.

Cause: The Max Retry Limit was reached while attempting to reconnect.

Action: Restart the XMPP driver to try again.
Level: 1

Type: ERROR

Impact: Process

SDP-26241: Reconnecting now... attempt #{0} for account {1}.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26241: Reconnecting now... attempt #{0} for account {1}.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26242: Reconnecting in {0} seconds for account {1}.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26242: Reconnecting in {0} seconds for account {1}.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

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-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-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-26246: Caught exception while closing connection of XMPP server.

Cause: Caught exception in XMPP driver while closing server connection.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26246: Caught exception while closing connection of XMPP server.

Cause: Caught exception in XMPP driver while closing server connection.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

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-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-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-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-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-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-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-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-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 has not been configured. Configure and restart this driver. Required Property: GatewayURL.

Cause: Proxy Driver was not configured.

Action: Configure and restart this driver. Required Property: GatewayURL.
Level: 1

Type: ERROR

Impact: Process

SDP-26256: Proxy Driver has not been configured. Configure and restart this driver. Required Property: GatewayURL.

Cause: Proxy Driver was not configured.

Action: Configure and restart this driver. Required Property: GatewayURL.
Level: 1

Type: ERROR

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-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-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-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-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-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-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-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-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-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-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-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 element was found for this Twitter Driver deployment. Create a configuration and restart this Twitter Driver.

Cause: No configuration element was found for this Twitter Driver deployment.

Action: Create a configuration and restart this Twitter Driver.
Level: 1

Type: ERROR

Impact: Process

SDP-26308: No configuration element was found for this Twitter Driver deployment. Create a configuration and restart this Twitter Driver.

Cause: No configuration element was found for this Twitter Driver deployment.

Action: Create a configuration and restart this Twitter Driver.
Level: 1

Type: ERROR

Impact: Process

SDP-26309: Twitter Driver not configured. Required property: AuthenticationMode

Cause: Twitter Driver not configured. Configure and restart this driver. Required properties: AuthenticationMode

Action: Configure and restart this driver.
Level: 1

Type: ERROR

Impact: Process

SDP-26309: Twitter Driver not configured. Required property: AuthenticationMode

Cause: Twitter Driver not configured. Configure and restart this driver. Required properties: AuthenticationMode

Action: Configure and restart this driver.
Level: 1

Type: ERROR

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-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-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-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-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-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-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-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-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-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-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-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 not configured. Configure and restart this driver. Required Properties: VoiceXMLOutboundServletURI.

Cause: VoiceXML Driver was not configured.

Action: Configure and restart this driver. Required Properties: VoiceXMLOutboundServletURI.
Level: 1

Type: ERROR

Impact: Process

SDP-26360: VoiceXML Driver not configured. Configure and restart this driver. Required Properties: VoiceXMLOutboundServletURI.

Cause: VoiceXML Driver was not configured.

Action: Configure and restart this driver. Required Properties: VoiceXMLOutboundServletURI.
Level: 1

Type: ERROR

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-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-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-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-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-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 element was found for this Extension Driver deployment. Create a configuration and restart this Extension Driver.

Cause: No configuration element was found for this Extension Driver deployment.

Action: Create a configuration and restart this Extension Driver.
Level: 1

Type: ERROR

Impact: Process

SDP-26453: No configuration element was found for this Extension Driver deployment. Create a configuration and restart this Extension Driver.

Cause: No configuration element was found for this Extension Driver deployment.

Action: Create a configuration and restart this Extension Driver.
Level: 1

Type: ERROR

Impact: Process

SDP-26454: Extension Driver not configured. Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.

Cause: Extension Driver was not configured.

Action: Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.
Level: 1

Type: ERROR

Impact: Process

SDP-26454: Extension Driver not configured. Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.

Cause: Extension Driver was not configured.

Action: Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.
Level: 1

Type: ERROR

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-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-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

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

24 TPC-00001 to TPC-90022

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}" may not be properly installed. Use Check for Update to install or 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. Enter a valid ID value.

Cause: No item with the specified ID exists.

Action: Enter a valid ID value.
Level: 1

Type: ERROR

Impact: Logging

TPC-00018: Specify your username.

Cause: The username cannot be empty.

Action: Provide data for the username.
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 a repository that is being used by any team(s). Make sure that no team is using the current 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-00035: Rename repository server error

Cause: The repository server name is invalid.

Action: Verify the repository server name.
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 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: Username, password and email field cannot be empty.

Cause: Empty username, 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.
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 and/or password.

Cause: Invalid username and/or password.

Action: Verify the login name and password.
Level: 1

Type: ERROR

Impact: Session

TPC-00068: Invalid server name and/or server port.

Cause: Invalid server name and/or server port.

Action: Verify the server name and/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: Save context exception: "{0}".

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.

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}". Make sure it does not exist.

Cause: The association is not unique.

Action: Specify a unique association for the role.
Level: 1

Type: ERROR

Impact: Logging

TPC-00102: Cannot revoke privilege "{0}" from role "{1}". Make sure it exists.

Cause: The association may 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 may 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.
Level: 1

Type: ERROR

Impact: Logging

TPC-00111: You have lost connection to TPC server. "{0}" Fix the problem and retry.

Cause: You have lost connection to the server for the reason mentioned.

Action: Log in to TPC server.
Level: 1

Type: ERROR

Impact: Logging

TPC-00112: Server did not send valid certificate.

Cause: Invalid certificate from server caused by the specified reason.

Action: Verify that you have specified correct server name and/or server port.
Level: 1

Type: ERROR

Impact: Logging

TPC-00113: You need a valid certificate to log in.

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: Unexpected problem during accepting the certificate. 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: You must specify a new password to commit. Click Cancel otherwise.

Cause: You either did not type in a new password or specify a blank new password.

Action: Specify a new password to commit and it cannot be blank. Hit Cancel otherwise.
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: Logging

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 "{0}".

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 specified invalid character(s)

Action: Provide valid repository name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00128: Query name cannot contain any of these characters: #/\?

Cause: The query name contains specified invalid character(s)

Action: Provide valid query name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00129: Tag name cannot contain any of these characters: #/\?

Cause: The tag name contains specified invalid character(s)

Action: Provide valid tag name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00130: 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-00131: Dependent field(s) "{0}" need input value(s).

Cause: Vvalues of the dependent fields are missing.

Action: Provide value(s) for the dependent fields.
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: Threads

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.

Cause: You have requested a service that is not supported by the server.

Action: Contact TPC Administrator.
Level: 1

Type: ERROR

Impact: Threads

TPC-60013: TPC client version "{0}" is not supported. Supported version is "{1}" or higher. Use Check for Update to upgrade your client.

Cause: Client and Server versions mismatched.

Action: Use Check for Update to upgrade the client.
Level: 1

Type: ERROR

Impact: Logging

TPC-60014: This client is no longer supported. Use Check for Update 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 Check for Update 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: TPC Server has terminated your session. Relogin to fix the problem.

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-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}". The server supports clients begining with version "{2}" or lower. 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 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-90001: Test failed. Make sure your username and password are correct.

Cause: Test failed.

Action: Make sure your username and password are correct.
Level: 1

Type: ERROR

Impact: Logging

TPC-90002: Cannot create connector record in the target database. Make sure the specified connector jar or bundle file is correct.

Cause: Cannot create connector record in the target database.

Action: Make sure the specified connector jar or bundle file is correct.
Level: 1

Type: ERROR

Impact: Logging

TPC-90003: Incorrect connector definition. Check the connector.xml file and make sure all required parameters are defined correctly.

Cause: Incorrect connector definition.

Action: Check the connector.xml file and make sure all required parameters are defined correctly.
Level: 1

Type: ERROR

Impact: Logging

TPC-90004: The local file name specified is not a jar or zip file. Select the correct file.

Cause: The local file name specified is not a jar or zip file.

Action: Select the correct file.
Level: 1

Type: ERROR

Impact: Logging

TPC-90005: Cannot find the file to install the selected connector.

Cause: Cannot find the file to install the selected connector.

Action: Make sure connector jar files are properly located.
Level: 1

Type: ERROR

Impact: Logging

TPC-90006: Cannot copy otpc.war file. Make sure the destination folder is not read only.

Cause: Cannot copy otpc.war file.

Action: Make sure the destination folder is not read only.
Level: 1

Type: ERROR

Impact: Logging

TPC-90007: Failed to create temporary directory.

Cause: Failed to create temporary directory.

Action: Check permission and space to create installation directory.
Level: 1

Type: ERROR

Impact: Logging

TPC-90008: Failed to deploy Team Productivity Center server.

Cause: Failed to deploy Team Productivity Center server.

Action: Check permission and space for deployment directory.
Level: 1

Type: ERROR

Impact: Logging

TPC-90009: Failed to install the selected connector.

Cause: Failed to install the selected connector.

Action: Check permission and space for installation directory and file.
Level: 1

Type: ERROR

Impact: Logging

TPC-90010: Installation failed. Review the system log.

Cause: Installation failed.

Action: Review the system log.
Level: 1

Type: ERROR

Impact: Logging

TPC-90011: The specified application server directory is not valid. Make sure the folder exists and is writable.

Cause: The specified Application Server directory is not valid.

Action: Make sure the folder exists and is writable.
Level: 1

Type: ERROR

Impact: Logging

TPC-90012: The otpc.war file specified does not function properly. The install image may be corrupted. Download a working copy of the installer.

Cause: The otpc.war file specified does not function properly.

Action: The install image may be corrupted. Download a working copy of the installer.
Level: 1

Type: ERROR

Impact: Logging

TPC-90013: JDBC Driver library path is not correct.

Cause: JDBC Driver library path is not correct.

Action: Corrrect JDBC Driver library path.
Level: 1

Type: ERROR

Impact: Logging

TPC-90014: Falied to add JDBC driver library to system class path.

Cause: Falied to add JDBC driver library to system class path.

Action: Review system log.
Level: 1

Type: ERROR

Impact: Logging

TPC-90015: JDBC driver class cannot be found.

Cause: JDBC driver class cannot be found.

Action: Make sure jdbc driver class is in appropriate jar file.
Level: 1

Type: ERROR

Impact: Logging

TPC-90016: No component has been selected. Select the components to install.

Cause: No component has been selected.

Action: Select the components to install.
Level: 1

Type: ERROR

Impact: Logging

TPC-90017: SQL Exception.

Cause: SQL Exception.

Action: Check system log.
Level: 1

Type: ERROR

Impact: Logging

TPC-90018: Cannot create database tables or populate seed data. Review the system log.

Cause: Cannot create database tables or populate seed data.

Action: Review the system log.
Level: 1

Type: ERROR

Impact: Logging

TPC-90019: Cannot connect to the specified database. Make sure all parameters are set correctly.

Cause: Cannot connect to the specified database.

Action: Make sure all parameters are set correctly.
Level: 1

Type: ERROR

Impact: Logging

TPC-90020: The file otpc.war already exists and cannot be overwritten. Make sure it is overwritable.

Cause: The file otpc.war already exists and cannot be overwritten.

Action: Make sure otpc.war is overwritable.
Level: 1

Type: ERROR

Impact: Logging

TPC-90021: Update failed. Check field values and try again.

Cause: Update failed.

Action: Check field values and try again.
Level: 1

Type: ERROR

Impact: Logging

TPC-90022: The version to be installed "{0}" is not newer than the current version "{0}".

Cause: The version for installation or upgrade is the same or lower than the current installation.

Action: Check for new version.
Level: 1

Type: ERROR

Impact: Logging

25 TRS-10000 to TRS-30030

TRS-10000: TRSConnectionMgr: DataSource is null.

Cause: DataSource is not set.

Action: Set DataSource first using MBeans.
Level: 1

Type: ERROR

Impact: Configuration

TRS-10001: Dispatcher failed to get jobs. {0}

Cause: SQLException

Action: Check database.
Level: 1

Type: ERROR

Impact: Data

TRS-10002: {0} failed to check job status. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10003: TxnReplayer URL:{0} is malformed. Replay item cannot be processed. {1}

Cause: Malformed TxnReplayer URL

Action: Change TxnReplayer URL specified in MBean or web.xml
Level: 1

Type: ERROR

Impact: Configuration

TRS-10004: Cannot open TxnReplayer URL:{0}. Replay item cannot be processed. {1}

Cause: TxnReplayer might not be running

Action: Check network. Make sure TxnReplayer is running
Level: 1

Type: ERROR

Impact: Network

TRS-10005: Dispatcher encountered an error during update of the REPLAY_USERS table. {0}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10006: JOB FAILED: clientId = {0}, JobId ={1}.

Cause: Job might be hanging or crashed.

Action: Consult administrator.
Level: 1

Type: ERROR

Impact: Data

TRS-10007: {0} failed to get database connection.

Cause: Database related

Action: Check database, or check DataSource.
Level: 1

Type: ERROR

Impact: Data

TRS-10008: Dispatcher failed to prepare SQL Statement. {0}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10009: Error creating DispatcherRuntimeInfo MBean. {0}

Cause: Open MBean metadata information cannot be constructed.

Action: Check MBean validity constraints.
Level: 1

Type: ERROR

Impact: Data

TRS-10010: Data source name: {0} cannot be resolved. Dispatcher thread will not start

Cause: Cannot resolve DataSource name

Action: Check DataSource name
Level: 1

Type: ERROR

Impact: Configuration

TRS-10011: {0} - error registering. {1}

Cause: MBean might already exist, or other reasons

Action: Ignore if MBean already exists. Otherwise consult administrator.
Level: 1

Type: ERROR

Impact: Data

TRS-10012: {0} - error querying number of jobs. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10013: {0} - error closing resultset. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10014: {0} - error closing statement. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10015: {0} - error querying replay items. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10016: {0} - error querying replay users. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10017: {0} - error querying replay types. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10018: DispatcherRuntimeInfo - error creating composite item. {0}

Cause: Open MBean related OpenDataException

Action: Consult administrator
Level: 1

Type: ERROR

Impact: Data

TRS-10019: DispatcherRuntimeInfo - error creating composite job. {0}

Cause: Open MBean related OpenDataException

Action: Consult administrator
Level: 1

Type: ERROR

Impact: Data

TRS-10020: {0} - error inserting replay type. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10021: {0} - error updating replay type. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10022: {0} - error removing replay items. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10023: {0} - error removing replay jobs. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10024: {0} - error removing replay users. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10025: {0} - error in database connection operations: commit, rollback or setAutoCommit. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10026: {0} - error loading settings. {1}

Cause: Error related to preference node

Action: Consult administrator
Level: 1

Type: ERROR

Impact: Data

TRS-10027: {0} - Cannot resolve DataSource Name {1}.

Cause: Cannot resolve DataSource

Action: Check DataSource name
Level: 1

Type: ERROR

Impact: Configuration

TRS-10028: {0} - DataSource name is null

Cause: DataSource name is null

Action: Check DataSource name in MBean or web.xml
Level: 1

Type: ERROR

Impact: Configuration

TRS-10029: {0} - error inserting replay items. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10030: {0} - Cannot find keystore password from Credential Store.

Cause: Cannot find keystore password

Action: Consult administrator
Level: 1

Type: ERROR

Impact: Security

TRS-10031: TRSConnectionMgr: fail to get database connection. {0}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10032: Cannot access Credential Store.

Cause: Credential store is not existing

Action: Consult administrator
Level: 1

Type: ERROR

Impact: Security

TRS-10033: Fail to get private key.

Cause: cannot get private key

Action: Check keystore, keystore password, certificate alias.
Level: 1

Type: ERROR

Impact: Security

TRS-10034: Client {0}, Replay item #{1}: Cannot update item status to {2}. {3}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10035: Client {0}, Replay item #{1}: Dependency not met. Parent item #{2} status is {3}.

Cause: Parent item status is not DONE

Action: Check parent item status
Level: 1

Type: ERROR

Impact: Data

TRS-10036: Client {0}, Replay item #{1}: Invalid Dependency #{2}.

Cause: DEPENDENCY value is not valid

Action: Check DEPENDENCY column for this item in table
Level: 1

Type: ERROR

Impact: Data

TRS-10037: Client {0}, Replay item #{1}: Fail to parse parameter. {2}

Cause: Cannot parse xml parameter

Action: Check PARAMS column for this item in table
Level: 1

Type: ERROR

Impact: Data

TRS-10038: Client {0}, Replay item #{1}: Error in retrieving password. {2}

Cause: Cannot get user's password

Action: Check security configuration
Level: 1

Type: ERROR

Impact: Security

TRS-10039: Client {0}, Replay item #{1}: Cannot find replay type class. {2}

Cause: Replay type class is missing

Action: Check to make sure the class library is available
Level: 1

Type: ERROR

Impact: Data

TRS-10040: Client {0}, Replay item #{1}: Cannot instantiate replay type class. {2}

Cause: Replay type class cannot be instantiated

Action: Class might be an interface or abstract
Level: 1

Type: ERROR

Impact: Data

TRS-10041: Client {0}, Replay item #{1}: Cannot find method with the right signature. {2}

Cause: No method available with the specified signature

Action: Check parameter provided in REPLAY_ITEM table
Level: 1

Type: ERROR

Impact: Data

TRS-10042: Client {0}, Replay item #{1}: Invocation access failure. {2}

Cause: Replay type method cannot be invoked

Action: The method does not have access to the definition of the specified class, field, method or constructor
Level: 1

Type: ERROR

Impact: Data

TRS-10043: Client {0}, Replay item #{1}, Calling Method = {2}, Class = {3}, Parameters = {4}: Invocation target failure. {5}

Cause: Replay type class cannot be invoked

Action: The invoked method throws an exception
Level: 1

Type: ERROR

Impact: Data

TRS-10044: Client {0}, Replay item #{1}: Unexpected exception. {2}

Cause: not known

Action: Check the error stack
Level: 1

Type: ERROR

Impact: Data

TRS-10045: Client {0}, Replay item #{1}: Unexpected error. {2}

Cause: not known

Action: Check the error stack
Level: 1

Type: ERROR

Impact: Data

TRS-10046: Query pending replay items for client {0} failed. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10047: Job #{0} for client {1} caught unexpected exception - {2}

Cause: The job is possibly determined dead by dispatcher or it has encountered other errors.

Action: Check the error stack
Level: 1

Type: ERROR

Impact: Data

TRS-10048: Cannot update job status to {0} for job id {1}.

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10049: Public key encryption is not set up properly. The feature is disabled.

Cause: Encryption configuration is not set up properly.

Action: Check public key encryption setup.
Level: 1

Type: ERROR

Impact: Security

TRS-10050: Default schema has not been set for user {0}, job {1}.

Cause: no default schema

Action: Set default schema in MBean
Level: 1

Type: ERROR

Impact: Configuration

TRS-10051: Caught RejectedExecutionException for user {0}, job {1}.

Cause: The job cannot be accepted for execution.

Action: Check thread pool
Level: 1

Type: ERROR

Impact: Configuration

TRS-10052: Thread pool is shut down for user {0}, job {1}.

Cause: Thread pool is shut down.

Action: Restart application.
Level: 1

Type: ERROR

Impact: Threads

TRS-10053: Missing ResourceBundle: {0}.

Cause: ResourceBundle is missing

Action: Check if resourcebundle is available
Level: 1

Type: ERROR

Impact: Data

TRS-10054: Client {0}, Replay item #{1}: Error processing the item.

Cause: Exception happened during processing this item

Action: Check log for errors logged before
Level: 1

Type: ERROR

Impact: Data

TRS-10055: Query outstanding replay items for client {0} failed. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10056: Worker servlet detects job {0} for client {1} has unexpected status. The job is not executed.

Cause: The job is determined dead by dispatcher, so it is not executed.

Action: Adjust failure recovery timeout if this error happens very frequently.
Level: 1

Type: ERROR

Impact: Data

TRS-10057: {0}: Failed to enable auto archive of replay jobs and replay items. {1}

Cause: IllegalArgumentException

Action: Check auto archive attributes
Level: 1

Type: ERROR

Impact: Data

TRS-10058: {0}: Failed to disable auto archive of replay jobs and replay items. {1}

Cause: IllegalArgumentException

Action: Make sure auto archive was previously enabled
Level: 1

Type: ERROR

Impact: Data

TRS-10059: Failed to create archive file {0}. {1}

Cause: Exception happened during creation of archive file

Action: Check database and make sure disk is not full
Level: 1

Type: ERROR

Impact: Data

TRS-10060: Failed to get value of attribute {0}.

Cause: Failed to get MBean attribute value

Action: Make sure attribute name is correct
Level: 1

Type: ERROR

Impact: Data

TRS-10061: Failed to set attribute {0} to {1}.

Cause: Failed to set MBean attribute value

Action: Make sure attribute name and value are correct
Level: 1

Type: ERROR

Impact: Data

TRS-10062: Database operation failed after retrying. Number of retries is {0}.

Cause: Database failure

Action: Check database.
Level: 1

Type: ERROR

Impact: Data

TRS-10063: Exception caught. Exiting Dispatcher thread.

Cause: Application is stopped or database failure.

Action: If it is database failure, check database.
Level: 1

Type: ERROR

Impact: Other

TRS-10064: Job Timeout triggered for client {0} for job {1} with status {2}. Updated time {3}, Timeout Value {4}

Cause: The job has been in the present state for more than the timeout value.

Action: Adjust failure recovery timeout if this error happens very frequently.
Level: 1

Type: ERROR

Impact: Data

TRS-10065: Failed to recover job {0} for client {1}

Cause: Database error may have occurred while updating job status to error.

Action: Check database connections.
Level: 1

Type: ERROR

Impact: Data

TRS-10066: Failed to query for the last processed item for client {0} and job {1}

Cause: Database error may have occurred while querying for replay items.

Action: Check database connections.
Level: 1

Type: ERROR

Impact: Data

TRS-10067: No items have been updated for client {0}

Cause: The item has been in the present state for more than the timeout value.

Action: Adjust item processing timeout if this error happens very frequently.
Level: 1

Type: ERROR

Impact: Data

TRS-10068: Failed to recover replay item for client {0} job {1}

Cause: Database error may have occurred while updating replay item status.

Action: Check database connections.
Level: 1

Type: ERROR

Impact: Data

TRS-10069: Received HTTP error code {0} for request {1}

Cause: Some error has occurred in the TxnReplayer component.

Action: Check log for errors logged before.
Level: 1

Type: ERROR

Impact: Data

TRS-10070: Cannot persist settings change for key: {0}, value: {1}

Cause: Some error has occurred in Java preference node persistent storage.

Action: Check default Java preference node storage location for your system.
Level: 1

Type: ERROR

Impact: Data

TRS-10071: Client {0}, Replay item #{1}: Custom Java class {2} cannot be found

Cause: Custom Java class is missing

Action: Check to make sure the custom Java class library is available
Level: 1

Type: ERROR

Impact: Data

TRS-10072: Client {0}, Replay item #{1}: Invalid parameter value {2} for the {3} of type {4} has been detected

Cause: Parameter value is not valid

Action: Check PARAMS column for this item in table
Level: 1

Type: ERROR

Impact: Data

TRS-10073: Client {0}, Replay item #{1}: Invalid parameter value for the {2} of type {3} has been detected. {4}

Cause: Parameter value is not valid

Action: Check PARAMS column for this item in table
Level: 1

Type: ERROR

Impact: Data

TRS-10074: Client {0}, Replay item #{1}: The value {2} of type char is empty

Cause: Parameter value is not valid

Action: Check PARAMS column for this item in table
Level: 1

Type: ERROR

Impact: Data

TRS-10075: Client {0}, Replay item #{1}: Invalid parameter value {2} {3} of type boolean has been detected

Cause: Parameter value is not valid

Action: Check PARAMS column for this item in table
Level: 1

Type: ERROR

Impact: Data

TRS-10076: Client {0}, Replay item #{1}: NULL is not a valid parameter value for the {2} of type {3}

Cause: Parameter value is not valid

Action: Check PARAMS column for this item in table
Level: 1

Type: ERROR

Impact: Data

TRS-10077: Cannot get Response from {0}. Replay item cannot be processed. {1}

Cause: TxnReplayer might not be running

Action: Check network. Make sure TxnReplayer is running
Level: 1

Type: ERROR

Impact: Network

TRS-10078: Client {0}, Replay item #{1}: the replay type has an invalid PASSWORD_TYPE value {2}.

Cause: Invalid PASSWORD_TYPE in REPLAY_TYPE table

Action: Provide valid value for the PASSWORD_TYPE column of the corresponding replay type in the REPLAY_TYPE table
Level: 1

Type: ERROR

Impact: Data

TRS-10079: Client {0}, Replay Item {1}: PARAMS column in REPLAY_ITEM table cannot be null or empty.

Cause: The PARAMS column in REPLAY_ITEM table is null or empty

Action: The PARAMS should have a value
Level: 1

Type: ERROR

Impact: Data

TRS-10080: TRS cannot publish the business event.

Cause: Client {0}, Item {1}: The event publication failed

Action: Check the following: (1) check the configuration (for example datasource) for event publication; (2) check the event payload; (3) check the DOM parser specified
Level: 1

Type: ERROR

Impact: Data

TRS-10081: Cannot parse property {0} for Replay type {1}. The property will be ignored.

Cause: The TYPE_PROPERTIES value for the replay type is in wrong format.

Action: Verify the value is a single string with a sequence of name value pairs, for example, "name1=value1;name2=value2;name3=value3;..."
Level: 1

Type: ERROR

Impact: Data

TRS-10082: Client {0}, Replay item #{1}: Application Module Configuration should not be empty for the replay type.

Cause: The ADF_CONFIG_NAME value for the replay type is empty.

Action: Provide valid value for ADF_CONFIG_NAME column in REPLAY_TYPE table for the replay type.
Level: 1

Type: ERROR

Impact: Data

TRS-10083: Client {0}, Replay item #{1}: Servlet URL should not be empty for the replay type.

Cause: The ReplayServletURL value for the replay type is empty.

Action: Provide valid ReplayServletURL value in TYPE_PROPERTIES column in REPLAY_TYPE table for the replay type.
Level: 1

Type: ERROR

Impact: Data

TRS-10084: Client {0}, Replay item #{1}: Cannot authenticate the user.

Cause: The username and password provided in replay item cannot be authenticated.

Action: Check the username and password for the replay item.
Level: 1

Type: ERROR

Impact: Data

TRS-10085: Client {0}, Replay item #{1}: Received error response from ReplayServlet with HTTP status code {2}. Detailed message: {3}

Cause: The server encountered error when processing the request.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Data

TRS-10086: Client {0}, Replay item #{1}: Cannot post to ReplayServlet due to transport error.

Cause: Cannot post to the ReplayServlet due to transport/network problems.

Action: Check the network or increase the timeout.
Level: 1

Type: ERROR

Impact: Data

TRS-10087: Client {0}, Replay item #{1}: Cannot post to ReplayServlet due to protocol violation.

Cause: There may be a mismatch between client and server in interpreting the HTTP specification.

Action: Report the bug.
Level: 1

Type: ERROR

Impact: Data

TRS-10088: Authentication failed because it cannot post to ReplayServlet due to transport error.

Cause: Cannot post to the ReplayServlet due to transport/network problems.

Action: Check the network or increase the timeout.
Level: 1

Type: ERROR

Impact: Data

TRS-10089: Authentication failed because it cannot post to ReplayServlet due to protocol violation.

Cause: There may be a mismatch between client and server in interpreting the HTTP specification.

Action: Report the bug.
Level: 1

Type: ERROR

Impact: Data

TRS-10090: Failed to validate credential for user {0} for replay type {1}.

Cause: Incorrect username or password.

Action: Check whether username or password is correctly set up for the replay type.
Level: 1

Type: ERROR

Impact: Data

TRS-19000: Entity Object {0} with key {1} not found.

Cause: The entity object row is not found in the database.

Action: Please check if the transaction needs to be changed and resubmitted.
Level: 1

Type: ERROR

Impact: Data

TRS-19001: Cannot find attribute {0} in Entity Object {1}.

Cause: The definition of attribute is not found in the entity object.

Action: Please make sure that the mobile entity object and server entity object have consistent attribute definitions.
Level: 1

Type: ERROR

Impact: Data

TRS-19002: Entity Object {0} with key {1} has an update conflict on attribute {2}. Current server-side value is ({3}), client-side old value is ({4}) and new value is ({5}).

Cause: The server value is different from the client's old value. Some other transaction(s) might have updated the server value since client's last synchronization.

Action: Please check if the transaction needs to be changed and resubmitted.
Level: 1

Type: ERROR

Impact: Data

TRS-20000: TRSConnectionMgr: invalid Database Retries is defined in MBeans. It is treated as no database retry.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

TRS-20001: Client {0}, Replay item #{1}: Plain user password is provided in REPLAY_ITEM table, which is not secure.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Security

TRS-20002: Client {0}, Replay item #{1}: The value {2} {3} of type char is longer than 1 character. Ignoring the rest of the characters.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

TRS-20003: {0} Preferences has invalid values. Reset using web.xml values.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

TRS-20004: {0} - error unregistering. {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

TRS-20005: {0} - cannot resolve backup DataSource name {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

TRS-20006: {0} failed to close statement. {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

TRS-20007: TRSConnectionMgr: failed to return connection to the pool. {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

TRS-20008: The system property {0} has value ({1}), which is different from the expected value ({2}).

Cause: The Java VM does not have the system property needed to support full features of TRS.

Action: Set the property or check documentation on its impact.
Level: 1

Type: WARNING

Impact: Configuration

TRS-20009: {0}: Failed to save archive attributes to preference node. {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

TRS-20010: {0}: Failed to remove archive attributes from preference node. {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

TRS-20011: TRSConnectionMgr is retrying to get connection. Number of times that TRSConnectionMgr retried:{0}

Cause: Database failure.

Action: Check database.
Level: 1

Type: WARNING

Impact: Configuration

TRS-20012: TRSDBExecutor is retrying the database operation. Number of times that TRSDBExecutor retried:{0}

Cause: Database failure.

Action: Check database.
Level: 1

Type: WARNING

Impact: Configuration

TRS-20013: A Replay Item for client {0} has been updated to status "ADMIN_REVIEW".

Cause: TxnReplayer failed while processing replay items.

Action: Adjust failure recovery timeout if this error happens very frequently.
Level: 1

Type: WARNING

Impact: Data

TRS-20014: {0} jobs to be submitted, but the expected number is {1} jobs.

Cause: Job query failed to pick up all new jobs.

Action: Increase dispatcher cycle time if this warning happens very frequently.
Level: 1

Type: WARNING

Impact: Data

TRS-20015: Client {0}, Replay item #{1}: USER_PASSWORD column is ignored for "CSF" password type.

Cause: User password is retrieved from credential store for replay types with "CSF" password type.

Action: Remove the value in USER_PASSWORD column in REPLAY_ITEM table for replay items with "CSF" password type.
Level: 1

Type: WARNING

Impact: Data

TRS-20016: {0} - Cannot access the MBean Server through JNDI: {1}. {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

TRS-20017: Test certificate is used for public key encryption.

Cause: Test certificate was configured as the default certificate for development purpose only.

Action: Use a secure certificate in a production environment.
Level: 1

Type: WARNING

Impact: Configuration

TRS-20018: {0}: Cannot close SQL result set. {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-20019: {0}: Cannot close SQL statement. {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-20020: {0}: Cannot close File Writer. {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30000: TRSConnectionMgr: using backup DataSource

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30001: Changing TxnReplayer URL from {0} to {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

TRS-30002: Changing Dispatcher loop delay from {0} to {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

TRS-30003: DispatcherListener: Starting Dispatcher thread.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Threads

TRS-30004: DispatcherListener: Stopping Dispatcher thread.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Threads

TRS-30005: The keystore provider is {0}. The keystore URL is {1}. The keystore type is {2}. The certificate alias is {3}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

TRS-30006: Client {0}, Replay item #{1}: Begin processing the item.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30007: Client {0}, Replay item #{1}: Successfully processed the item.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30008: Client {0}, Replay item #{1}: Checking replay item dependency.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30009: Client {0}, Replay item #{1}: Calling Method={2}, Class={3}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

TRS-30010: Client {0}, Replay item #{1}: Invoking method {2} of Class {3} succeeded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

TRS-30011: Client {0}, Replay item #{1}: Use custom XSD {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30012: Client {0}, Replay item #{1}: Use custom XSL {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30013: Public key encryption is disabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

TRS-30014: {0}: Inserted item {1} successfully.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30015: {0}: Enabling auto archive of replay jobs and replay items

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30016: Auto archive is enabled. Archive Time is {0}. Archive Interval is {1}. Archive Age is {2}. Archive Path is {3}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30017: {0}: Successfully removed {1} replay items

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30018: {0}: Successfully removed {1} replay jobs

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30019: Removing replay jobs older than {0} and with job status DONE or ERROR

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30020: Removing replay items older than {0} and with any status but PENDING, PROCESSING or ADMIN_REVIEW

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30021: Successfully created archive file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30022: Recovering job {0} for client {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30023: Recovering replay items for client {0} and job {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30024: Persist setting changes for key: {0}, value: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30025: {0}: Successfully removed {1} lone replay items

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30026: {0}: Successfully removed {1} parent/child replay items

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30027: {0}: Successfully removed {1} replay items in total

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30028: Successfully disabled auto archive of replay jobs and replay items

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30029: Publish business event

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30030: Successful credential validation for user {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

26 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

27 UPGAST-00001 to UPGAST-00267

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: Run the command again, specifying 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: Run the command again, specifying 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: Managed 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 is not a valid Oracle WebLogic domain.

Action: Specify an existing WebLogic domain directory or specify a non-existent domain.
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: One of the upgrade steps was looking for an MBean with this name. That might or might not be an error, depending on context.

Action: See the secondary error message for additional details.
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-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: Run the command again, specifying 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: 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-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-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 template.

Cause: The plugin is doing something inconsistently.

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: Specify a response file generated by the Upgrade Assistant.
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: Specify a response file generated by the Upgrade Assistant for this installation.
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 prevents 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 prevents 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 upgrade/components/ directory of it's Oracle 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 Fusion Middleware home.

Cause: Either this Middleware 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 Fusion Middleware home, yet a response file was specified.

Cause: Either this Middleware 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 Assistant log files. Correct the problem before running the 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 check list the contents of schema version registry table for the component failed because 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 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 check list the contents of schema version registry table for the component failed because no registry entry exists 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 Oracle Home {1}.

Cause: Component names must be unique with a Fusion Middleware Home. Either the component descriptor files are incorrect, or multiple copies of the same component have been installed in the same FMW 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 'text' attribute. This is required.

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 responase 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 necessesary 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-00267: 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

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

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.

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, 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.

Third-Party Content, Products, and Services Disclaimer

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

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction 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.