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

11g Release 2 (11.1.2.0.0)

E22506-01

Contents

Title and Copyright Information

Preface

- Audience

- Documentation Accessibility

- Conventions

1 ADF_FACES-00001 to ADF_FACES-60104

2 ADF_TRINID-00001 to ADF_TRINID-30336

3 ADFC-00001 to ADFC-14008

4 ADFDI-00100 to ADFDI-55516

5 ADFF_BIND-00001 to ADFF_BIND-00046

6 BDSS-00000 to BDSS-65160

7 CLONE-27010 to CLONE-28400

8 DVT-02012 to DVT-26021

9 HELP-00001 to HELP-30008

10 JBO-24000 to JBO-80008

11 MDS-00001 to MDS-91023

12 RCS-00001 to RCS-23000

13 TPC-00001 to TPC-90049

14 TPCTEST-00001 to TPCTEST-00001

15 UIX-00001 to UIX-00025

Oracle® Fusion Middleware

Error Messages Reference

11g Release 2 (11.1.2.0.0)

E22506-01

May 2011

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

E22506-01

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

Primary Author: Peter Jacobsen

Contributing Author: Promila Chitkara

Contributor: Buddhika Kottahachchi

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 software or related documentation 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 RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software 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 which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

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

Preface

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

Audience

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

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html 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-60104

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: Bundle {0} for helpTopicId={1} not found.

Cause: The resource bundle for the specified helpTopicId was not found.

Action: Ensure a help provider 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-00025: Unable to tear down the visiting context due to {0}.

Cause: Unable to tear down the visiting context.

Action: Look for other exceptions that may have caused this failure.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-00026: The {0} facet for component type {1} does not contain a component of the required type {2}.

Cause: The facet is not returning a component of the correct type.

Action: Check the facet to make sure it contains a component of the correct type.
Level: 1

Type: SEVERE

Impact: Logging

ADF_FACES-00027: The {0} facet for component type {1} has multiple children when only a single child is allowed.

Cause: The facet contains multiple children, only a single child is allowed.

Action: Check the facet to make sure it contains only one component.
Level: 1

Type: SEVERE

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. Expected {0}, but got {1}.

Cause: During 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 implementation 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-10025: During the evaluation of an include attribute, the context could not be torn down. Ensure that the attributes are not being accessed from a different include context.

Cause: During the evaluation of an include attribute, the context could not be torn down.

Action: Ensure that the attributes are not being accessed from a different include context.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-10026: During the processing of the region component, either a context change was not found or it did not match the instance set up by the current component. Expected {0} but found {1}.

Cause: During the processing of the region component, either a context change was not found or it did not match the instance set up by the current component.

Action: Contact Oracle Support Services.
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-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-30176: Your application is running in production mode, but you have enabled the profiler in your web.xml file. Please check if this setting is desired.

Cause: The web.xml contains a configuration setting that enables the profiler.

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

Type: WARNING

Impact: Logging

ADF_FACES-30177: Your application is running in production mode, but you have enabled the automation in your web.xml file. Please check if this setting is desired.

Cause: The web.xml contains a configuration setting that enables the automation.

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

Type: WARNING

Impact: Logging

ADF_FACES-30178: Your application is running in production mode, but you have enabled Asserts within ADF Faces. Please check your web.xml file if this is desired.

Cause: The web.xml contains a configuration setting that enables Asserts within ADF Faces.

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

Type: WARNING

Impact: Logging

ADF_FACES-30179: For more information, please see the server's error log for an entry beginning with: The UIViewRoot is null. Fatal exception during PhaseId: {0}.

Cause: The UIViewRoot is null.

Action: See the server's error log for more information.
Level: 1

Type: SEVERE

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-30181: Active Data has been disabled.

Cause: Active Data Service is not supported in a portlet environment.

Action: Active Data is currently not supported to work in a portlet environment.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30182: The number of sitemap XML entries exceeded the limit of 50 000

Cause: ADF Faces does not support generating sitemaps with more than 50 000 entries

Action: Use other means to generate sitemaps with more than 50 000 entries
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-60087: Failed to locate a facet to be relocated. The component must have been removed from the component tree when it should not have been. Expected to find the component under component with client ID "{0}" with relative search path "{1}".

Cause: A required component was removed from the component tree

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60088: Component with ID: {0} was not reregistered for being automatically re-rendered.

Cause: The component has not been previously registered for being automatically re-rendered.

Action: Make sure the component has been previously registered for being automatically re-rendered before calling reregisterComponentForPPR (FacesContext context, UIComponent component).
Level: 2

Type: 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-60090: Active Data Service DataUpdateManager is NULL

Cause: The DataUpdateManager is NULL for the current page.

Action: None.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60091: Attempting to add requested listener to component of type: {0} has failed. For the type: {0}, the resetListener tag requires that the component publishes the event: {1}.

Cause: For the type given, there was no appropriately named add method for the resetListener 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 resetListener tag.
Level: 2

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

ADF_FACES-60093: The resetListener tag must be a child of UIComponent.

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

Action: Move resetListener tag so that it is a child of a UIComponent.
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-60095: During the processing of the form renderer, the context change found did not match the expected component.

Cause: During the processing of the form renderer, the context change found did not match the expected component.

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

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 ADF exception handlders.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-60099: The region component with id: {0} has detected a page fragment with multiple root components. Fragments with more than one root component may not display correctly in a region and may have a negative impact on performance. It is recommended that you restructure the page fragment to have a single root component.

Cause: A page fragment with multiple roots was detected by the region component.

Action: Please restructure the fragment to have a single root component.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-60100: An error occurred while processing your request. For more information, please see the server's error log for an entry beginning with HTTP Error Status Code: {0}"

Cause: An exception was thrown durring a PPR request.

Action: Please look in the server error logs for more details on this error.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-60101: HTTP Error Status Code: {0}."

Cause: An error occurred in the HTTP server which prevented it from fulfilling the request.

Action: Please refer to the status code returned by the server to help resolve the issue, or contact your system administrator for further assistance.
Level: 1

Type: SEVERE

Impact: Logging

ADF_FACES-60102: Unable to determine the viewId for the current request. A null viewId will be set for the header Adf-View-id.

Cause: The UIViewRoot instance is null for the current request.

Action: A null viewId will be set in the response header for the current request.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-60103: JSF version is not sufficient to run this application.

Cause: JSF version is lower than the required version for this application.

Action: Check your environment and validate the JSF libraries on the application class path.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60104: Unable to encode the value {0} for name {1}, so writing null instead.

Cause: Unable to encode the value for sending to the client.

Action: Check your value. For example, you could have a value set in your clientAttribute component that cannot be javascript encoded to send to the client.
Level: 1

Type: WARNING

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

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-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: ''{0}'' ''{1}''.

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-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-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}'' does not evaluate to a boolean.

Cause: A router activity case contained an EL expression that did not evaluate to a boolean.

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

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 reading the DIRemoteServlet 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-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-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-00503: A validation error occurred for metadata property {0}.

Cause: An invalid property value was specified in the configuration metadata.

Action: Consult the client logs and exception details for more information.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-00504: A validation warning occurred for metadata property {0}.

Cause: An invalid property value was specified in the configuration metadata.

Action: Consult the client logs and exception details for more information.
Level: 1

Type: WARNING

Impact: Configuration

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-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-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-05508: An invalid list item is selected: {0}.

Cause: An invalid list item was found while transferring data from a worksheet to the model.

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-05583: Unable to execute the command '{0}' while a worksheet has an active filter. Remove the filter. Then, retry the operation.

Cause: The specified command was attempted while an Excel filter was active.

Action: Remove the filter. Then, retry the operation.
Level: 1

Type: WARNING

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-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-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-07503: cannot open workbook file {0}

Cause: A failed attempt was made to open the workbook file.

Action: Ensure that sufficient disk space is present and that user has has the necessary privileges to open the workbook file.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07507: given buffer size is incorrect; given: {0}

Cause: An incorrect value was supplied for the Workbook Parameters buffer size.

Action: Ensure that compatible versions of the client and server framework are in use. Check the workbook configuration and retry the operation with a different workbook.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07508: did not find expected start tag; found: {0}

Cause: The workbook's internal format may be corrupted.

Action: Ensure that compatible versions of the client and server framework are in use. Check the workbook configuration and retry the operation with a different workbook.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07509: did not find expected end tag; found: {0}

Cause: The workbook's internal format may be corrupted.

Action: Ensure that matching versions of the client and server framework are in use. Check the workbook configuration and retry the operation with a different workbook.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07510: mode length is incorrect; found: {0}

Cause: The workbook's internal format may be corrupted.

Action: Ensure that compatible versions of the client and server framework are in use. Check the workbook configuration and retry the operation with a different workbook.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07511: AppRoot length is incorrect; found: {0}

Cause: The workbook's internal format may be corrupted.

Action: Ensure that compatible versions of the client and server framework are in use. Check the workbook configuration and retry the operation with a different workbook.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07512: Workbook initialization parameters length is incorrect; found: {0}

Cause: The workbook's internal format may be corrupted.

Action: Ensure that compatible versions of the client and server framework are in use. Check the workbook configuration and retry the operation with a different workbook.
Level: 1

Type: ERROR

Impact: Session

ADFDI-07513: Destination length {0} is less than found length {0}.

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-07514: unable to create HttpWebRequest

Cause: A failed attempt was made to create an http web resource.

Action: Check the configuration of the workbook to ensure that the web resource begins with http or https.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-07515: invalid response status code: {0}

Cause: A failed attempt was made to access an http web resource.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

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-07523: Failed to delete worksheet

Cause: The document may be corrupted.

Action: Obtain a fresh copy of the document.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-07524: 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-07525: failed to suppress application alerts

Cause: An attempt was made to suppress the display of alerts.

Action: Review the log files for additional details.
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 desigern 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-07534: Unable to verify Trust Center setting. The Trust Center setting 'Trust access to the VBA project object model' is required for {0}.

Cause: There was an unexpected problem while attempting to verify the Excel setting 'Trust access to the VBA project object model'.

Action: Activate the setting 'Trust access to the VBA project object model' by visiting the Excel Trust Center.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-07535: Unable to activate the Trust Center setting 'Trust access to the VBA project object model'. This setting is required for {0}.

Cause: There was an unexpected problem while attempting to activate the Excel setting 'Trust access to the VBA project object model'.

Action: Activate the setting 'Trust access to the VBA project object model' by visiting the Excel Trust Center.
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-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: unknown desktop integration error

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-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-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. 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 BDSS-00000 to BDSS-65160

BDSS-00000: DispatcherSettings - error loading settings. {0}

Cause: Cannot load the preferences node for BDSS.

Action: Verify that the preferences back-end store exists and that the user this application is running under has correct access rights.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-00005: Exception thrown by backing store when setting ChunkSize: {0}

Cause: Cannot store data to the preferences node for BDSS.

Action: Verify that the preferences back-end store exists and that the user this application is running under has correct access rights.
Level: 1

Type: ERROR

Impact: Data

BDSS-00006: Exception thrown by backing store when setting EngineEndpointUrl: {0}

Cause: Cannot store data to the preferences node for BDSS.

Action: Verify that the preferences back-end store exists and that the user this application is running under has correct access rights.
Level: 1

Type: ERROR

Impact: Data

BDSS-00010: Cannot retrieve the backing store to load preferences.

Cause: Cannot retrieve the preferences node for BDSS.

Action: Verify that the preferences back-end store exists and that the user this application is running under has correct access rights.
Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-00011: Cannot initialize SyncDispatcherBean.

Cause: There is either improper configuration or BDSS components are not installed correctly.

Action: Verify your configuration and reinstall the BDSS components if necessary.
Level: 1

Type: ERROR

Impact: Data

BDSS-00012: User chunk size is not available from configuration. Using the default.

Cause: Cannot retrieve the data from the preferences node for BDSS.

Action: Verify that the preferences back-end store exists and that user this application is running under has correct access rights.
Level: 1

Type: WARNING

Impact: Configuration

BDSS-00014: ArrayOutOfBounds exception occurred!

Cause: The code referenced an array index that does not exist.

Action: Restart the application.
Level: 1

Type: ERROR

Impact: Data

BDSS-00015: Cannot get users to dispatch from configuration!

Cause: The list of users to synchronize was not returned by the BDSS configuration.

Action: Verify that there are users that are configured properly using the User Settings MBean.
Level: 1

Type: ERROR

Impact: Data

BDSS-00017: Calling SynchronizeUsers failed: {0}

Cause: The call to the operation SynchronizeUsers failed.

Action: Verify that the BDSS hub components are installed on your applications server and are accessible.
Level: 1

Type: ERROR

Impact: Data

BDSS-00019: A member of the input users array was an empty string or was null. Continuing to process other users.

Cause: A hub user login was stored as an empty string.

Action: Verify that all hub users have a non-empty string for their login.
Level: 1

Type: NOTIFICATION

Impact: Data

BDSS-10001: Failed to allocate an object of type {0}.

Cause: Failed to allocate an object of the type specified.

Action: Ensure that the system is not running low on memory. Check the log for other errors that may have led to this problem. Try restarting the appropriate component or machine.
Level: 1

Type: ERROR

Impact: Other

BDSS-10002: Null object detected. Context: {0}

Cause: A null object has been detected. The object name or type is logged with this message.

Action: Examine the log to determine the cause of this problem.
Level: 1

Type: ERROR

Impact: Other

BDSS-10004: Original Error already logged.

Cause: This indicates that an exception has been detected, although details of the primary error are not logged with this message to avoid duplicate logging of an error. The primary error which caused this exception should already be logged.

Action: Examine the log for an earlier log entry that indicates the primary error which caused this exception.
Level: 1

Type: ERROR

Impact: Other

BDSS-10005: Object {0} is invalid.

Cause: A component in the BDSS product has detected an invalid object that is expected to be valid. For example, the object may be null, or it may be an empty string, etc. The invalid object may be a function parameter or an object retrieved by other means.

Action: Try checking configuration. Try restarting components or the machine. Try reinstalling the appropriate BDSS component. Examine the log for other messages that may indicate the cause of this problem.
Level: 1

Type: ERROR

Impact: Data

BDSS-10006: Failed to access EJB due to problem with object {0}.

Cause: Indicates that an error occurred when attempting to access an Enterprise Java Bean.

Action: Examine the log to determine the cause for this error as an exception cause may have been logged with this message. Ensure that the product is properly installed.
Level: 1

Type: ERROR

Impact: Other

BDSS-10007: Version Id

Cause: This message string is a label that identifies a PIM record version ID. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Other

BDSS-20001: An unrecoverable error occurred while pushing record change(s) to the target PIM. Aborted pushing additional events to the PIM.

Cause: The cause is unknown but has been caught by a Java Exception. The exception occurred while the Sync-Engine was in the process of pushing record change events to a connector.

Action: Search the BDSS log for the exception text that should give a clue to the cause.
Level: 1

Type: ERROR

Impact: Data

BDSS-20004: Failed to create a new record. The Sync-Engine will continue to push any additional create-record actions to the target PIM. Source-PIM record data: {0}

Cause: A failure code was returned from the target connector when the Sync-Engine invoked its createRecord method.

Action: Ensure that the target PIM and PIM connector is installed and working correctly. Look in the target connector log for clues to the failure.
Level: 1

Type: ERROR

Impact: Data

BDSS-20005: Failed to update a PIM record. The Sync-Engine will continue to push any additional update-record actions to the target PIM.

Cause: The Sync-Engine detected an error while attempting to update a PIM record.

Action: Ensure that the target PIM and PIM connector are installed and working correctly. Look in the Sync-Engine log and the target connector log for clues to identify the failure.
Level: 1

Type: ERROR

Impact: Data

BDSS-20006: Failed to update a PIM record.

Cause: The Sync-Engine has detected an exception while in the process of updating a PIM record. The failure may be due to a problem in the hub, rather than a connector issue.

Action: Examine the Sync-Engine log for the exception text that should give a clue as to why the failure occurred.
Level: 1

Type: ERROR

Impact: Data

BDSS-20007: Source PIM record data:

Cause: This message is simply used as a label to identify the source PIM record data that is logged immediately following this label text. This message is appended to a primary error message and is never logged by itself.

Action: No action is required specifically for this error message. Instead, see the action defined for the primary error message to which this error message is appended.
Level: 1

Type: ERROR

Impact: Other

BDSS-20009: The target PIM connector failed to delete a PIM record. The Sync-Engine will attempt to push any additional delete-record actions to target PIM.

Cause: The Sync-Engine has detected an error while attempting to delete a PIM record.

Action: Examine the Sync-Engine log for information about the error cause.
Level: 1

Type: ERROR

Impact: Data

BDSS-20010: Failed to write an error status message to a PIM metadata record for Connector {0}, Hub Domain {1}, PIM User {2} PIM record ID {3}.

Cause: The Sync-Engine detected an error while preparing to write an error message to the database for a particular PIM Map Record.

Action: Examine the Sync-Engine log to find the underlying exception message.
Level: 1

Type: ERROR

Impact: Data

BDSS-20012: Failed to delete a PIM record.

Cause: The Sync-Engine has detected an exception while in the process of deleting a PIM record. The failure may be due to a problem in the hub, rather than a connector issue.

Action: Examine the Sync-Engine log for the exception text that should give a clue as to why the failure occurred.
Level: 1

Type: ERROR

Impact: Data

BDSS-20013: Failed to update metadata to the BDSS hub-record. \tSource Connector user = {0} \tSource PIM Connector Name = {1} \tSource PIM Record Identifier = {2}.

Cause: This error occurs when the Sync-Engine is unable to persist updated metadata to the BDSS database for a particular BDSS hub-record. In particular, this error occurs when the Sync-Engine catches an exception when invoking method SyncConfig::getHubRecordForPimRecord. This error could indicate corrupt metadata for a particular BDSS hub-record, or perhaps a network or database failure, or a problem with the SyncConfig component.

Action: Check that the database is accessible. Perhaps try restarting the BDSS hub. If corrupt metadata is suspected, then try removing all metadata for a user and perform initial synchronization for a user.
Level: 1

Type: ERROR

Impact: Data

BDSS-20014: Failed to update the error code for a record.

Cause: The Sync-Engine cannot find a hub record for the specified PIM record identifier and Connector. This problem is unexpected and should not occur under normal operating conditions. This error message signifies that either hub metadata is missing or incorrect, or there was some other problem - such as a database access error. The Sync-Engine detects this error by means of an Exception thrown from SyncConfig method getHubRecordForPimRecord.

Action: Examine the log for evidence of exception text that will give more specific information as to the cause of the problem. Ensure that all infrastructure, such as the database and network, are working correctly. Ensure that all configuration is correct. Ensure that metadata is not corrupt for the specified user, Connector user and PIM Connector Name and PIM Record identifier. If the problem is due to hub metadata corruption for a given user then try clearing that user hub metadata and perform first-time synchronization for the user.
Level: 1

Type: ERROR

Impact: Data

BDSS-20015: Failed to find an BDSS PIM metadata record for BDSS master hub record ID = {0}

Cause: This error message is logged when a PIM metadata record could not be found for the specified hub user ID, hub record ID and Connector. In particular, the Sync-Engine logs this message when it detects an exception from method SyncConfig::getPimRecordForHubRecord. This problem could be due to corrupt metadata (e.g. the PIM metadata record is actually missing) or some other cause.

Action: Examine the log for the exception text that should give a better clue as to the underlying cause of the error. Ensure that all infrastructure, such as the database and network, are working correctly. Ensure that all configuration is correct. Ensure that hub metadata is not corrupt for the logged hub record ID. If the problem is due to hub metadata corruption for a given user then try clearing that user hub metadata and perform first-time synchronization for the user.
Level: 1

Type: ERROR

Impact: Data

BDSS-20016: The Hub User {0} is already being synchronized and cannot be synchronized again until that session has ended.

Cause: A new sync session cannot be started until the old session has ended.

Action: Wait for the original sync session to finish. If a new sync session for the Hub User still cannot be started, restart the BDSS Hub.
Level: 1

Type: ERROR

Impact: Data

BDSS-20017: (Target Connector user)

Cause: This message string is a label for a Connector user identifier that is a destination target for record events that are being pushed to a PIM connector. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 1

Type: NOTIFICATION

Impact: Other

BDSS-20018: (Target PIM Connector Name)

Cause: This message string is a label for the name of a PIM connector that is a destination target for record events that are being pushed to a PIM. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 1

Type: NOTIFICATION

Impact: Other

BDSS-20019: BDSS queue message receiver timeout expired. Queue message not received.

Cause: This error indicates that the Sync-Engine ExtractResponseTimeout occurred because the Sync-Engine did not receive an ExtractResponse for which it was waiting. In particular, this error represents a failure to receive an ExtractResponse via a queue message in a timely fashion. The Sync-Engine uses the ExtractResponseTimeout as a time-trigger to determine when a connector has become unresponsive. In such a case, the Sync-Engine has determined that it will not receive an ExtractResponse in a timely fashion and thus takes recovery action to abort the synchronization. This problem could be caused when a connector does not correctly send an ExtractResponse to the Sync-Engine. Alternatively, the ExtractResponse was sufficiently large, or network latency slow enough, that the timeout occurred before the ExtractResponse could be properly transferred to the Sync-Engine from a connector.

Action: Ensure that all connectors are properly working and can successfully send ExtractResponse objects to the Sync-Engine. Ensure that the Sync-Engine machine is not overloaded and can handle receiving ExtractResponse objects efficiently. Ensure that the amount of data transferred via an ExtractResponse is not too large, or the network latency too slow, to trigger the ExtractResponseTimeout. If necessary, increase the ExtractResponseTimeout timeout value. Determine whether an http webservice timeout is occurring when a connector sends an ExtractResponse to the Sync-Engine.
Level: 1

Type: ERROR

Impact: Data

BDSS-20020: Received queue message that is an unexpected message class type. Expecting class type ObjectMessage. {0}.

Cause: This error indicates that the Sync-Engine has received a queue message with an unexpected Java class type. This error suggests a communication protocol failure within the Sync-Engine.

Action: Ensure the BDSS product is installed and configured correctly and ensure that a rogue producer is not sending messages to the BDSS message queue.
Level: 1

Type: ERROR

Impact: Data

BDSS-20021: Invalid Hashtable element key.

Cause: This error indicates that the Sync-Engine has detected an invalid hash table element key.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-20022: Invalid Hashtable element value for key = {0}.

Cause: This error indicates that the Sync-Engine has detected an invalid hash table element value for the specified element key.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-20023: null Hub User ID detected in an element of UsersArray.

Cause: The Sync-Engine has detected an invalid hub-user in the UsersArray. The Sync-Engine cannot synchronize an invalid hub user. In particular, a string array element is null, instead of specifying a valid hub user.

Action: Ensure that the array of users sent to the Sync-Engine has a valid hub user for each element in the array.
Level: 1

Type: ERROR

Impact: Data

BDSS-20024: Invalid Hub User ID detected in an element of UsersArray.

Cause: The Sync-Engine has detected an invalid hub-user in the UsersArray. The Sync-Engine cannot synchronize an invalid hub user. In particular, a valid string array element has been detected, but the string is empty and does not specify a hub user.

Action: Ensure that the array of users sent to the Sync-Engine has a valid hub user for each element in the array.
Level: 1

Type: ERROR

Impact: Data

BDSS-20026: Must configure a user hub-domain synchronization between two connector URLs. Currently detecting {0} URLs.

Cause: Specifies that an invalid number of connector URLs have been identified for synchronization of a hub domain for a user. Synchronization can only occur between two connector URLs for a given user and hub domain.

Action: Validate that BDSS configuration is correct for synchronizing between two connectors.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-20027: Synchronization cannot start because the Hub user ID provided is either null or an empty string.

Cause: The Hub user id provided is either null or an empty string.

Action: Verify that the mechanism used to start synchronization is providing a non-null non-empty value for the Hub User.
Level: 1

Type: ERROR

Impact: Data

BDSS-20028: Invalid ExtractResponse detected. The ExtractResponse sent by a connector indicates that it contains delete events but the delete events do not exist.

Cause: This error occurs when the Sync-Engine detects that an ExtractResponse specifies a true value for member ExtractResponse.ExtractResponseData.hasDeletes and yet specifies a null value for member ExtractResponse.ExtractResponseData.deleteRecordIdArray. Thus, the ExtractResponse object is corrupt and cannot be processed.

Action: Fix the connector that is providing the invalid ExtractResponse.
Level: 1

Type: ERROR

Impact: Data

BDSS-20029: Invalid ExtractResponse detected. The ExtractResponse sent by a connector contains a null delete record ID.

Cause: This error is logged when the Sync-Engine detects a null array element in member ExtractResponse.ExtractResponseData.deleteRecordIdArray when a valid delete record ID is expected.

Action: Fix the connector that is providing the invalid ExtractResponse.
Level: 1

Type: ERROR

Impact: Data

BDSS-20030: An ExtractResponse indicates that upserts exist but they do not.

Cause: This error occurs when the Sync-Engine determines that an ExtractResponse should contain upsert records when it does not. In particular, the member ExtractResponse.ExtractResponseData.hasUpserts is true but upsertRecordArray in ExtractResponse.ExtractResponseData.upsertRecordArray is invalid.

Action: Fix the connector that is providing the invalid ExtractResponse.
Level: 1

Type: ERROR

Impact: Data

BDSS-20035: Cannot find a PIM connector endpoint for the current user and Connector {0}

Cause: The Sync-Engine queried all connector URLs for a particular Connector using connector interface method getPimServerEndPoint. However, none of the connector instances provided a connector endpoint for a particular Connector user.

Action: See the log entry to identify the Connector and the corresponding hub user ID for this error. Ensure that the Connector user is configured in the PIM, that BDSS configuration is correct, that all connector instance URLs are properly configured, and that the connector instance can successfully return the endpoint for the Connector and user for which this problem occurs.
Level: 1

Type: ERROR

Impact: Data

BDSS-20040: An error occurred while pushing create, update or delete changes to Connector {0} for hub domain {1}.

Cause: This is a generic high-level error message indicating that an error occurred while pushing create, update, or delete events to the specified Connector and hub domain.

Action: Examine this message in the log to find the pertinent Connector and hub domain. Examine the log for the underlying error that is expected to have been logged prior to this error message. Take appropriate action once the underlying error has been identified.
Level: 1

Type: ERROR

Impact: Data

BDSS-20041: The BDSS Engine will continue to push record changes to the next PIM if any are available.

Cause: The text of this informational message is a supplement to the text of message SYNCENG_PUSH_TO_PIM_ERROR. This message text is logged only when the Sync-Engine has changes to additional PIMs that can be propagated for the same hub domain.

Action: No action is necessary that is specific to this message. Instead, see the action text for error message SYNCENG_PUSH_TO_PIM_ERROR.
Level: 1

Type: ERROR

Impact: Data

BDSS-20043: Unexpected or failure result code detected in an ExtractResponse. ExtractResponse Result Code = {0}. ExtractResponse Error Description = {1}

Cause: An ExtractResultCode value of either PARTIAL_EXTRACT_COMPLETED_OK or PARTIAL_EXTRACT_COMPLETED_NOTOK has been detected in an ExtractResponse received from a connector. An ExtractResponse, with either of these ExtractResultCode values, is considered nonviable for synchronization by the Sync-Engine. Thus, the Sync-Engine cannot perform synchronization with the corresponding ExtractResponse.

Action: Examine the connector, PIM server and configuration corresponding to the failed ExtractResponse. Fix the problem with this connector-related error.
Level: 1

Type: ERROR

Impact: Data

BDSS-20044: Unknown failure code detected in an ExtractResponse. ExtractResponse Result Code = {0}. ExtractResponse Error Description = {1}

Cause: The Sync-Engine detects an unknown ExtractResultCode value in an ExtractResponse received from a connector.

Action: Examine the connector, PIM server and configuration corresponding to the failed ExtractResponse. Fix the problem with this connector-related error.
Level: 1

Type: ERROR

Impact: Data

BDSS-20045: Unknown Connector detected when retrieving an extract response.

Cause: The Sync-Engine recognizes only two Connectors - one for Exchange and the other for Webcenter. The Connector, received in an ExtractResponse from a connector, is not recognized by the Sync-Engine.

Action: Examine the log entry for this message to obtain the Connector retrieved from the problematic ExtractResponse. Examine the connector, PIM server and configuration corresponding to the problematic ExtractResponse. Ensure that the connector provides the correct PIM server type in the ExtractResponse objects it sends to the Sync-Engine.
Level: 1

Type: ERROR

Impact: Data

BDSS-20046: Error getting ExtractResponse objects.

Cause: This message indicates that the Sync-Engine detected an error while receiving ExtractResponse objects during a synchronization session. The underlying problem should already have been logged.

Action: Examine earlier log messages, just prior to this log message, to identify the underlying problem.
Level: 1

Type: ERROR

Impact: Data

BDSS-20047: Null name-key object detected in PIM record description array.

Cause: This error occurs when the Sync-Engine is comparing records using their key fields and detects that the name of a field is invalid, in other words empty or null, for an UpsertRecord provided by a connector ExtractResponse.

Action: Ensure that key-field configuration is correct. Examine recent ExtractRequests in the log to help determine which connector is providing an invalid key-field. Ensure that all connectors are providing valid ExtractRequest responses to the Sync-Engine.
Level: 1

Type: ERROR

Impact: Data

BDSS-20048: An Exception error occurred during synchronization.

Cause: An exception has been detected in the Sync-Engine during synchronization.

Action: Examine the log file for information about this exception.
Level: 1

Type: ERROR

Impact: Data

BDSS-20049: Unable to access FtsLogger class object while processing an Exception error. Exception: {0}.

Cause: An exception has been detected in the Sync-Engine during synchronization. However, the Sync-Engine is unable to log the session ID and hub user ID with this message.

Action: Examine the log file for information about this exception.
Level: 1

Type: ERROR

Impact: Data

BDSS-20050: Invalid Engine Endpoint URL received from configuration. URL is null or empty string.

Cause: An invalid Sync-Engine endpoint URL has been returned from method SyncConfig::getEngineEndPointURL, without the method having thrown an exception.

Action: Confirm that a valid engine endpoint URl is configured.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-20052: Hub domain synchronization failed.

Cause: This message indicates that an error was detected while synchronizing a particular hub domain. The hub user, synchronization session identifier and hub domain are logged with this message.

Action: Examine this message in the log to determine which hub domain failed. Examine the log to find the underlying cause of the failure.
Level: 1

Type: ERROR

Impact: Data

BDSS-20053: Failed to send extract request.

Cause: An error was detected while attempting to send an extract request to a connector.

Action: Examine the log to determine the underlying problem which caused the error.
Level: 1

Type: ERROR

Impact: Data

BDSS-20054: Failed to initialize connector user synchronization session. BDSS presumes the connector instance URL is invalid and will clear the connector endpoint for hub user: {0}, Connector: {1}. Synchronization will be attempted in a subsequent sync cycle.

Cause: An error was detected while invoking connector method initializeUserSyncSession.

Action: Examine the log to determine the underlying problem which caused the error. Expect to find the hub user ID, Connector and a description of the underlying exception in the log.
Level: 1

Type: ERROR

Impact: Data

BDSS-20057: Failed connector initialization.

Cause: An error was detected while attempting to initialize the connectors involved in synchronization for a hub-user.

Action: Examine the log to determine the underlying problem which caused the error.
Level: 1

Type: ERROR

Impact: Data

BDSS-20058: Unable to get a connector instance URL for the configured connector endpoint for hub user: {0}, Connector: {1}. The failed connector endpoint will be cleared for this user so a new connector endpoint can be configured during the next synchronization cycle.

Cause: The Sync-Engine was not able to get a connector endpoint for the hub user and Connector specified in this message.

Action: Examine the log entry for information about the underlying exception, and to identify the hub user and Connector for which the problem occurred.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-20059: Unable to get valid connector instance URL for hub user: {0}, Connector: {1}.

Cause: The Sync-Engine has determined that a connector instance URL is invalid, either empty or null, even though an exception did not occur while attempting to retrieve the connector instance URL.

Action: Examine the log message to determine the hub user and Connector for which this error occurred. Ensure that all connector instance URL and endpoint configuration is correct. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-20060: Failure detected when attempting to invoke connector method {0}.

Cause: An exception has been detected while invoking the connector method specified by this message.

Action: Examine the log to determine the hub user ID and Connector corresponding to this failure. Also, examine the log to determine which connector method failed.
Level: 1

Type: ERROR

Impact: Other

BDSS-20061: Unable to configure connector endpoint for current hub user and Connector.

Cause: The Sync-Engine detected an exception thrown from method m_SyncConfig.setConnectorEndPoint.

Action: Ensure that configuration and installation are correct. Examine this message in the log to determine the corresponding hub user ID and Connector.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-20062: "Connector method {0} returned error code {1}."

Cause: The Sync-Engine has detected an error code returned from a connector method.

Action: Examine the log to determine which connector method failed and the error code it returned.
Level: 1

Type: ERROR

Impact: Other

BDSS-20063: Detected an invalid message type. Expecting type javax.jms.MapMessage. {0}

Cause: The SyncUserMDB Message Driven Bean has erroneously received a queue message that is not of type javax.jms.MapMessage. SyncUserMDB retrieves messages from a Weblogic Server in-memory queue. It retrieves queue messages having message property RECIPIENT = BDSS SyncUser MDB Recipient.

Action: Ensure that no other software products are sending messages to the configured WLS in-memory queue with queue message having property RECIPIENT = BDSS SyncUser MDB Recipient. For reference, content of the erroneous queue message is appended to this log entry. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-20084: PIM Record Description:

Cause: This message string is a label whose purpose is to indicate that PimRecordDescription metadata is being logged for a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Data

BDSS-20085: Field Name

Cause: This message string is a label that identifies a single PimRecordDescription field name for a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Data

BDSS-20086: Field Value is null

Cause: This message string indicates that a PimRecordDescription.descriptionArray object contains a KeyValuePair object with a null field value. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. Also, fix the cause of this null field value within the PimRecordDescription metadata of a PIM record.
Level: 1

Type: ERROR

Impact: Data

BDSS-20087: Field Value

Cause: This message string is a label that identifies a single PimRecordDescription field value for a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Data

BDSS-20088: The description array is empty

Cause: This string is never logged by itself but is only ever appended, to another primary logged message string, to provide ancillary information. The primary message may be an error or may simply be a debug message. This message indicates that a PimRecordDescription information is not available. In this case, the PimRecordDescription object is valid, and contains a valid KeyValuePair array object, but the KeyValuePair array has no elements.

Action: See the log for the primary logged message to determine whether any action is needed.
Level: 1

Type: ERROR

Impact: Data

BDSS-20089: The description array is null

Cause: This string is never logged by itself but is only ever appended, to another primary logged message string, to provide ancillary information. The primary message may be an error or may simply be a debug message. This message indicates that PimRecordDescription information is not available for a PIM record. In this case, the PimRecordDescription object is valid but contains a null KeyValuePair array.

Action: See the log for the primary logged message to determine whether any action is needed.
Level: 1

Type: ERROR

Impact: Data

BDSS-20092: No PimRecordDescription data is provided in this record

Cause: This string is never logged by itself but is only ever appended, to another primary logged message string, to provide ancillary information. The primary message may be an error or may simply be a debug message. This message indicates that PimRecordDescription information is not available, for a PIM record, because the PimRecordDescription object is null.

Action: See the log for the primary logged message to determine whether any action is needed.
Level: 1

Type: ERROR

Impact: Data

BDSS-20093: A null field name is detected for a PimRecordDescription field name.

Cause: This message string indicates that a field name is null within the PimRecordDescription metadata of a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. Also, fix the cause that is producing this null field name.
Level: 1

Type: ERROR

Impact: Data

BDSS-20094: ErrorCode

Cause: This message string is a label that identifies an error code. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message.
Level: 1

Type: ERROR

Impact: Other

BDSS-20095: Hub Domain

Cause: This message string is a label that identifies a hub domain identifier. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Other

BDSS-20096: Hub User

Cause: This message string is a label that identifies a hub user ID. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Other

BDSS-20097: SessionID

Cause: This message string is a label that identifies a user synchronization session ID. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Other

BDSS-20098: Connector user

Cause: This message string is a label that identifies a Connector user ID. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Other

BDSS-20099: Connector Name

Cause: This message string is a label that identifies a PIM connector name. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 1

Type: NOTIFICATION

Impact: Other

BDSS-20100: PIM Record Id

Cause: This message string is a label that identifies a PIM record ID. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Other

BDSS-20102: Error detected when attempting to delete BDSS master hub metadata record {0}.

Cause: This message indicates that an exception occurred when attempting to delete a hub metadata record from the BDSS database. In particular, method SyncConfig::deleteHubMapRecord threw an exception. The cause of the exception is logged with this message.

Action: See the log to find the exception cause that is logged with this message.
Level: 1

Type: ERROR

Impact: Data

BDSS-20103: Failed to delete an BDSS Pim-Map metadata record corresponding to specified PIM record.

Cause: This message indicates that an exception occurred when attempting to delete a PIM map record from the BDSS database. In particular, method SyncConfig::deletePimMapRecord threw an exception. The cause of the exception is logged with this message.

Action: See the log to find the exception cause that is logged with this message.
Level: 1

Type: ERROR

Impact: Data

BDSS-20104: Hub domain synchronization succeeded.

Cause: This is an informational message that indicates that synchronization has succeeded. The hub-user, sync-session ID, Connector and hub-domain are logged with this message.

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: Other

BDSS-20106: Started synchronization for user

Cause: This is an informational message that indicates when a synchronization session has started for a hub user. The hub user is specified in the log message header.

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: Other

BDSS-20107: A user synchronization session has ended. User sync status is {0}.

Cause: This is an informational message that indicates when a hub user synchronization session has ended. In particular, the call to method SyncConfig::setUserSyncSessionToEnded has succeeded. This notification does not imply whether domain synchronization succeeded or not for this same synchronization session. The hub user is specified in the log message header.

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: Other

BDSS-20108: Failed to end a user synchronization session.

Cause: This error message indicates that a hub user synchronization session did not end successfully. In particular, the call to method SyncConfig::setUserSyncSessionToEnded threw an exception. This error does not imply whether domain synchronization succeeded or not for this same synchronization session. The hub user is specified in the log message header.

Action: No specific action recommended. However, check configuration - perhaps for the hub user in particular. Also suggest restarting the BDSS application server, or reinstalling BDSS.
Level: 1

Type: ERROR

Impact: Other

BDSS-20109: Hub-domain {0} will not be synchronized for Connector {1} because no other Connector is configured to synchronize it for the current hub-user.

Cause: Hub-user configuration, for the specified hub-domain, is set to synchronize the hub-domain using only a single Connector. It is invalid to synchronize a hub-domain by only a single Connector. The Sync-Engine has modified its only local copy of configuration, for the current hub-user sync-session, so that it will not synchronize the specified hub-domain for the current hub-user sync-session.

Action: Fix configuration for the specified hub-user so that the specified hub-domain is configured to synchronize by more than one Connector. Alternatively, remove the specified hub-domain from configuration for the specified hub-user.
Level: 1

Type: WARNING

Impact: Configuration

BDSS-20110: Connector {0} will not be synchronized, for the current hub-user sync-session, because it is not configured to synchronize any hub-domains.

Cause: The Sync-Engine has determined that hub-user configuration, for the specified Connector, is not valid because it is not configured to synchronize any hub-domains. The specified Connector will not be allowed to synchronize for the current hub-user sync-session.

Action: Ensure that configuration, for the specified hub-user and Connector, is correct for synchronizing at least one hub-domain with another Connector.
Level: 1

Type: WARNING

Impact: Configuration

BDSS-20111: AttendeeMetadata:

Cause: This message string is a label that is used when AttendeeMetadata is being logged for a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Data

BDSS-20112: Organizer

Cause: This message string is a label that is used when AttendeeMetadata is being logged for a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Data

BDSS-20113: VEventStartDate

Cause: This message string is a label that is used when AttendeeMetadata is being logged for a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Data

BDSS-20114: Required Attendees

Cause: This message string is a label that is used when AttendeeMetadata is being logged for a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Data

BDSS-20115: Optional Attendees

Cause: This message string is a label that is used when AttendeeMetadata is being logged for a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Data

BDSS-20116: Non Attendees

Cause: This message string is a label that is used when AttendeeMetadata is being logged for a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Data

BDSS-20117: None

Cause: This message string is a label that is used when AttendeeMetadata is being logged for a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 1

Type: ERROR

Impact: Data

BDSS-30001: The engine setting for {0} is invalid.

Cause: The Engine Settings for this parameter are invalid.

Action: Use the EngineSettings MBean to enter a valid value for this parameter.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30003: Error during construction of SyncConfig. {0}

Cause: There was an out of memory error or SyncConfig cannot get EngineSettings MBean.

Action: Verify that the EngineSettings MBean was deployed or verify that there was sufficient memory.
Level: 1

Type: ERROR

Impact: Other

BDSS-30006: Cannot find section {0} in profile {1}.

Cause: The configuration data for that profile and section cannot be retrieved from the data store.

Action: Verify that the profile and section exist in the data store and that the data store can be reached.
Level: 1

Type: ERROR

Impact: Other

BDSS-30007: EngineSettings - error loading settings. {0}

Cause: Cannot find the engine settings in the preferences store or cannot load the preferences store.

Action: Verify that the preferences store exists on the server and that it is accessible.
Level: 1

Type: ERROR

Impact: Data

BDSS-30011: A {0} was detected when attempting to set the {1} configuration option. {2}

Cause: Cannot find the engine settings in the preferences store, cannot load the preferences store or cannot write to the preferences store.

Action: Verify that the preferences store exists on the server and that it is accessible.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30012: A {0} was detected when attempting to invoke the MBean operation. {1}

Cause: The BDSS MBeans are not accessible or were not successfully installed.

Action: Using the Application Server administration UI, verify that the BDSS MBeans were installed correctly.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30013: A {0} was detected when converting profile data: Profile = {1}, Section = {2}, Parameter = {3}, Value = {4}.

Cause: There was an error converting the Profile settings returned from the database to a format that will display properly.

Action: Try the operation again. If the error persists, check the data in the database or reinstall the Profile Settings MBean.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30014: Failed to build open mbeaninfo.

Cause: There was an error loading the MBeans.

Action: Try restarting the MBean console or reinstalling the MBeans.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30015: Operation name cannot be null.

Cause: There was an error loading the MBeans because an operation name was null.

Action: Try reinstalling the MBeans.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30016: Cannot call invoke with null operation name.

Cause: There was an error loading the MBeans because an operation name was null.

Action: Try reinstalling the MBeans.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30017: An error occurred when invoking MBean operation {0}. Exception Class Name = {1}. Caught [{2}].

Cause: There was an error running the operation.

Action: Try the operation again. If the error persists, check the data in the database or reinstall the MBeans.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30018: Cannot find MBean operation {0}.

Cause: There was an error finding the MBean operation.

Action: Try the operation again. If the error persists, using the Application Server administration UI, verify that the BDSS MBeans were installed correctly.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30019: Cannot invoke operation {0} because an invalid parameter was provided to the MBean.

Cause: An invalid parameter was given to the MBean.

Action: Try the action again with valid parameters. If the error continues, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30020: Error converting the server map. {0}

Cause: There was an error converting the server map returned from the database to a format that will display properly.

Action: Try the operation again. If the error persists, check the data in the database or reinstall the Server and Connectors MBean.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30021: Error converting the connector map. {0}

Cause: There was an error converting the connector map returned from the database to a format that will display properly.

Action: Try the operation again. If the error persists, check the data in the database or reinstall the Server and Connectors MBean.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30022: Error getting hub users. {0}

Cause: This may be an error in the configuration of the Hub User or the Hub User does not exist.

Action: Ensure that the hub user exists in configuration and is configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30023: Error getting Connector users. {0}

Cause: This may be an error in the configuration of the Connector user or the Connector user does not exist.

Action: Ensure that the Connector user exists in configuration and is configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30024: Error getting domains. {0}

Cause: This may be an error in the configuration of the domain.

Action: Ensure that the domain exists in configuration and is configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-30025: Error getting records. {0}

Cause: This may be an error in the database for the record.

Action: Ensure that the record exists in the database.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35001: Cannot create a Connector user with the login {0} and cannot map the user to the hub user {1}.

Cause: The data store was not accessible or the record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the record exists in configuration
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35002: The configuration parameter {0} in the section {1} of the profile {2} cannot be deleted.

Cause: The configuration was not accessible.

Action: Ensure your database is running and you can log in to it from a client.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35003: Cannot delete the record with an id of {0}.

Cause: The data store was not accessible or the user does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the user exists in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35004: Cannot find the hub record with an id of {0} for user {1}.

Cause: The data store was not accessible or the user or record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the user and record exist in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35005: Cannot find the hub record for the PIM record with an id of {0} for user {1}.

Cause: The data store was not accessible or the record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the record exists in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35006: Cannot find the hub user {0}.

Cause: The data store was not accessible or the user does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the hub user exists in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35007: Cannot find the {0} LOV with a value of {1}.

Cause: The data store was not accessible or the record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the record exists in configuration
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35008: Cannot find the {0} object with an id of {1}.

Cause: The data store was not accessible or the record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the record exists in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35009: Cannot find the PIM record with an id of {0}.

Cause: The data store was not accessible or the user or record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the user and record exist in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35010: Cannot find the PIM record with an id of {0} for user {1}.

Cause: The data store was not accessible or the user or record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the user and record exist in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35011: Cannot find the PIM record for the hub record with an id of {0} for user {1}.

Cause: The data store was not accessible or the record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the record exists in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35012: Cannot find the Connector user with the ID of {0} for the Connector named {1}.

Cause: The data store was not accessible or the record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the record exists in configuration
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35013: Cannot find the record associated data for the record {0}.

Cause: The data store was not accessible or the user or record data does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the user and record exist in configuration.
Level: 32

Type: TRACE

Impact: Configuration

BDSS-35014: Cannot return users from the data source.

Cause: The data store was not accessible or the record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the record exists in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35015: Cannot retrieve {0} records for user {1}.

Cause: The data store was not accessible or the user does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the user exists in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35016: Cannot remove the {0} object with an id of {1}.

Cause: The data store was not accessible or the record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the record exists in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35017: Cannot update the sync level for the domain {0} for the Connector named {1}.

Cause: The data store was not accessible or the record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the record exists in configuration
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35018: Cannot update the hub record with an id of {0} for user {1}.

Cause: The data store was not accessible or the record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the record exists in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35019: Cannot update or create the {0} object with an id of {1}.

Cause: The data store was not accessible or the record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the record exists in configuration
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35020: Cannot update the PIM record with an id of {0} for user {1}.

Cause: The data store was not accessible or the record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the record exists in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35021: Cannot update the session for hub user {0}.

Cause: The user cannot be found in configuration or the data store is not allowing the update.

Action: Ensure your data store is running and you can log in to it from a client and that the hub user exists in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35022: The configuration parameter {0} in the section {1} of the profile {2} cannot be written to the data store.

Cause: The configuration was not accessible or cannot be written to.

Action: Ensure your database is running and you can log in to it from a client.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35023: Cannot store record associated data for the record with an id of {0}.

Cause: The data store was not accessible or the user does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the user exists in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35024: Cannot store record description data for the record with an id of {0}.

Cause: The data store was not accessible or the user or record does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the user and record exist in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35025: Cannot write user associated data for user {0}.

Cause: The data store was not accessible or cannot be written to.

Action: Ensure your data store is running and you can log in to it from a client.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35026: Cannot write the {0} domain sync status for user {1} on the Connector named {2}.

Cause: The data store was not accessible or cannot be written to or configuration for this user is corrupted.

Action: Ensure your data store is running and you can log in to it from a client. Also ensure the configuration for this user is correct.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35027: The configuration for the Connector {0} has an error.

Cause: There is an error in the configuration of this Connector.

Action: Review the configuration for this Connector and resolve the problem.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35028: The configuration for the domain {0} has an error.

Cause: There is an error in the configuration of this domain.

Action: Review the configuration for this domain and resolve the problem.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35029: One of the Connector user mappings is invalid for hub user {0}.

Cause: The configuration for one of the hub user to Connector user mappings is corrupted or not present.

Action: Ensure that the mapping exists in configuration and is valid.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35030: The configuration for the Connector instance {0} is not correct. Review the configuration for {1}.

Cause: There was missing configuration for this Connector instance.

Action: Review the configuration for this Connector instance and correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35031: The configuration for the PIM domain {0} is not correct. Review the configuration for {1}.

Cause: There was missing configuration for this domain.

Action: Review the configuration for this domain and correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35032: The configuration for the user {0} is not correct. Review the configuration for the user on Connector {1}.

Cause: There was missing configuration for this user.

Action: Review the configuration for this user and correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35033: The Connector user for Connector {0} does not exist for hub user {1}, or there is more than one Connector user with this name configured for this Connector.

Cause: This hub user had no Connector user associated to it for the Connector.

Action: Review the configuration for this user and correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35034: The configuration for the Connector {0} is not correct. Review the configuration for {1}.

Cause: There was missing configuration for this Connector.

Action: Review the configuration for this Connector and correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35035: The configuration for the profile {0} is does not exist. Review the configuration for the profile.

Cause: There was missing configuration for this profile.

Action: Review the configuration for this profile and correct any configuration problems if needed.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35036: The configuration parameter {0} in the section {1} of the profile {2} does not exist.

Cause: There was missing configuration for this profile.

Action: Review the configuration for this profile and correct any configuration problems if needed.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35037: There is no {0} for the user {1}.

Cause: There was missing configuration for this user.

Action: Review the configuration for this user and correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35038: The configuration for the PIM server {0} has an error.

Cause: There is an error in the configuration of this PIM server.

Action: Review the configuration for this PIM server and resolve the problem.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35039: A Connector user with a login of {0} already exists for the Connector {1}.

Cause: The configuration for at least one of the Connector users already exists. Verify this user is not already in configuration and that this is the correct ID for the Connector.

Action: Ensure that the mapping exists in configuration and is valid.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35040: The user is not in the same session whose ID is {0}.

Cause: The session ID for the user is not the same as the stored session ID. This may be due to 2 separate BDSS engines processing the same user.

Action: Ensure only one BDSS dispatcher is running at a time and that the user is not stuck in a sync session.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35041: Cannot store associated data for the user {0}.

Cause: The data store was not accessible or the user does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the user exists in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35042: Cannot store metadata for the user {0}.

Cause: There was an error while storing the configuration of this user.

Action: Verify the database can be accessed and that the BDSS configuration is correct.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35043: Cannot store a record for the user {0}.

Cause: The data store was not accessible or the user does not exist in configuration.

Action: Ensure your data store is running and you can log in to it from a client and that the user exists in configuration.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35044: There were too many {0} records found for {1}.

Cause: There were too many records found that matched the query.

Action: Ensure your configuration is correct and that the user's data is not corrupted
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35045: The configuration for the user {0} has an error.

Cause: There is an error in the configuration of this user.

Action: Review the configuration for this user and resolve the problem.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35046: Cannot find the associated data for user {0}.

Cause: The associated data for the user is not in the database.

Action: This may not be an error if this is the first time sync for the user. If not, verify the user is in the database and the database is accessible.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35051: Cannot store the cached sync state for the user {0}.

Cause: There was an error while storing the cached sync state of this user.

Action: Verify the database can be accessed, that the BDSS configuration is correct and the cached sync state exists.
Level: 1

Type: ERROR

Impact: Data

BDSS-35052: Cannot store the permanent sync state for the user {0}.

Cause: There was an error while storing the permanent sync state of this user.

Action: Verify the database can be accessed, that the BDSS configuration is correct.
Level: 1

Type: ERROR

Impact: Data

BDSS-35053: Could not obtain the Pim Record Versions for Connector User {0}, HubDomain {1}, Connector {2}. Exception detected: {3}.

Cause: There was an error while attempting to obtain the Pim Record Version identifiers from the BDSS database for this user.

Action: Verify the database can be accessed and that the BDSS configuration is correct.
Level: 1

Type: ERROR

Impact: Data

BDSS-35054: An invalid Connector domain synchronization level has been detected.

Cause: An invalid Connector domain synchronization level has been detected in configuration.

Action: Review Connector domain synchronization level configuration and correct it.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35055: An invalid Connector user synchronization level has been detected.

Cause: An invalid Connector user synchronization level has been detected in configuration.

Action: Review Connector user synchronization level configuration and correct it.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35057: There is more than one record with the Hub user login of {0}.

Cause: There is more than one hub user with this login. This is a configuration error.

Action: Review the configuration for this user and correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35063: Cannot find the domain {0} for Connector user Id {1}.

Cause: The supplied domain does not exist for the Connector user. This could be a configuration error.

Action: Review the configuration for this user and correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35070: Cannot find the PIM server instance {0} for Connector {1}.

Cause: Cannot update the PIM server instance. This could be a configuration error.

Action: Review the configuration for this PIM server instance and correct any configuration problems.
Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-35071: Cannot find the domain {0} for the Connector named {1}.

Cause: Cannot update the domain. This could be a configuration error.

Action: Review the configuration for this domain and correct any configuration problems.
Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-35072: Cannot update the filter {0} for the domain {1} for the Connector named {2}.

Cause: Cannot update the domain filter. This could be a configuration error.

Action: Review the configuration for this domain and correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35073: Cannot find the LOV for the PIM server type {0}.

Cause: Cannot find the LOV for the PIM server type. This could be a configuration error.

Action: Review the LOVs, ensure you are using the correct LOV and correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35074: Cannot create or update the connector {0}.

Cause: Cannot create or update the connector. This could be a configuration error or a database access error.

Action: Review the configuration and database connect information. Then correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35075: Cannot delete the connector {0}.

Cause: Cannot delete the connector. This could be a configuration error or a database access error.

Action: Review the configuration and database connect information. Then correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35077: Cannot delete the filter {0} for the domain {1} for the Connector named {2}.

Cause: Cannot delete the domain filter. This could be a configuration error.

Action: Review the configuration for this domain and correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35078: Cannot get connector details.

Cause: Cannot get the details for the connectors. This could be a configuration error or a database access error.

Action: Review the configuration and database connect information. Then correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35079: Error converting the connector instance map. {0}

Cause: There was an error converting the connector instance map returned from the database to a format that will display properly.

Action: Try the operation again. If the error persists, check the data in the database or reinstall the Servers and Connectors MBean.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35080: Error converting the domain map. {0}

Cause: There was an error converting the domain map returned from the database to a format that will display properly.

Action: Try the operation again. If the error persists, check the data in the database or reinstall the Servers and Connectors MBean.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35081: Error converting the domain filter map. {0}

Cause: There was an error converting the domain filter map returned from the database to a format that will display properly.

Action: Try the operation again. If the error persists, check the data in the database or reinstall the Servers and Connectors MBean.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35083: Missing configuration for PROFILE_NAME = {0}, SECTION_NAME = {1}, PARAMETER name = {2}.

Cause: A required configuration record does not exist in database table PROFILES for the criteria specified in the log message.

Action: Review the configuration for this profile and correct any configuration problems. In particular, ensure that a record exists for the specified criteria.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35084: Invalid configuration value for an existing record in database PROFILES table for PROFILE_NAME = {0}, SECTION_NAME = {1}, PARAMETER name = {2}.

Cause: The content of the VALUE column is invalid for a record in the database PROFILES table that matches the specified profile name, section name and parameter name.

Action: Review the configuration for matching profile record and correct any configuration problems. In particular, ensure the database VALUE column is populated correctly for matching record.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-35085: Cannot remove temporary sync state for Connector user = {0}, Connector Name = {1}, Hub Domain = {2}.

Cause: The Sync-Engine cannot remove old state data for the specified Connector user, Connector and Hub Domain. This problem is unexpected and should not occur under normal operating conditions. This error message signifies a database access error which could be caused by a database deadlock or inability to contact the database.

Action: Examine the log for evidence of exception text that will give more specific information as to the cause of the problem. Ensure that all infrastructure, such as the database and network, are working correctly.
Level: 1

Type: ERROR

Impact: Data

BDSS-35086: Cannot create a UserContextState for Connector user = {0}, Connector Name = {1}, Hub Domain = {2}.

Cause: The Sync-Engine cannot create a record in the database to save the sync state for the specified Connector user, Connector and Hub Domain. This problem is unexpected and should not occur under normal operating conditions. This error message signifies a database access error which could be caused by a database deadlock or inability to contact the database.

Action: Examine the log for evidence of exception text that will give more specific information as to the cause of the problem. Ensure that all infrastructure, such as the database and network, are working correctly.
Level: 1

Type: ERROR

Impact: Data

BDSS-35087: Cannot read history data.

Cause: The Sync-Engine cannot read the history table. This problem is unexpected and should not occur under normal operating conditions. This error message signifies a database access error which could be caused by a database deadlock or inability to contact the database.

Action: Examine the log for evidence of exception text that will give more specific information as to the cause of the problem. Ensure that all infrastructure, such as the database and network, is working correctly.
Level: 1

Type: ERROR

Impact: Data

BDSS-60001: Unable to get the connector instance web service URL.

Cause: Unknown. See recommended action.

Action: Examine the log and, if available, especially the stack trace and exception cause chain for the cause.
Level: 1

Type: ERROR

Impact: Programmatic

BDSS-60002: An error occurred in connector interface method {0}.

Cause: Unknown. See recommended action.

Action: Examine the log, especially the stack trace and exception cause chain for the cause.
Level: 1

Type: ERROR

Impact: Other

BDSS-60003: Parameter {0} is null.

Cause: The specified Java method argument is null.

Action: Examine the exception stack trace to determine which method failed.
Level: 1

Type: ERROR

Impact: Programmatic

BDSS-60004: Parameter {0} is an empty String object.

Cause: The specified Java method argument is an empty String object.

Action: Examine the exception stack trace to determine which method failed.
Level: 1

Type: ERROR

Impact: Programmatic

BDSS-60005: Parameter {0} is an empty List object.

Cause: The specified Java method argument is an empty List object.

Action: Examine the exception stack trace to determine which method failed.
Level: 1

Type: ERROR

Impact: Programmatic

BDSS-60006: Method failed with result {0}.

Cause: May be caused by a failure in RuntimeLibraryWrapper methods setUserAssociatedData or setRecordAssociatedData.

Action: The caller of the RuntimeLibraryWrapper method must examine the returned Map to determine the particular failure details.
Level: 1

Type: ERROR

Impact: Other

BDSS-60007: Failed to build a record description field list. The value for hub field {0} is not available.

Cause: The specified hub field value could not be found when creating a record field description list.

Action: Review configuration for record description fields.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-60008: PIM Transport provided too many PimExtractResponse objects.

Cause: More than one PimExtractResponse object has been received by the generic connector component.

Action: Ensure the PimTransport only provides a single PimExtractResponse to the generic connector component.
Level: 1

Type: ERROR

Impact: Programmatic

BDSS-60009: Failed to load PIM transport class {0}

Cause: The generic connector component failed to load the specified PIM transport adapter class.

Action: Ensure that the PIM transport adapter class is configuration and deployed correctly.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-60010: Failed to find PIM transport class name for the following configuration parameters. ConnectorName = {0}, Section = {1}, Parameter = {2}

Cause: The generic connector component failed to find the specified PIM transport adapter class in configuration.

Action: Ensure that configuration specifies the correct PIM transport adapter class name.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-60011: Cannot get PimDomainInfo using arguments syncSessionId {0} and pimUserId = {1}

Cause: Internal corruption in the generic connector.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BDSS-60012: Cannot find PimDomainInfo using arguments syncSessionId {0}, pimUserId = {1} and hubDomainName = {2}

Cause: Internal corruption in the generic connector.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BDSS-60013: Failed to extract. Sending an error ExtractResponse to the hub.

Cause: Internal corruption in the generic connector.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BDSS-60014: Failed an attempt to exceed the allowable ExtractResponse batch size.

Cause: A PIM Transport has attempted to exceed the maximum ExtractResponse batch size allowed for a PimExtractResponse object.

Action: Examine the exception stack trace, in the log, to determine whether failure occurred when adding a delete-record event or an upsert-record event to the PimExtractResponse cache. Fix the PIM Transport so it doesn't exceed the allowable maximum batch size.
Level: 1

Type: ERROR

Impact: Programmatic

BDSS-60016: Configuration value not found for the following configuration parameters. Profile = {0}, Section = {1}, Parameter = {2}

Cause: The generic connector component cannot find a configuration value in the BDSS database for the specified profile name, section name and parameter name.

Action: Ensure that configuration exists in the BDSS database for the specified profile name, section name and parameter name.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-60018: Error Code

Cause: This message string is a label that identifies an error code. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message.
Level: 32

Type: TRACE

Impact: Logging

BDSS-60019: Hub Domain

Cause: This message string is a label that identifies a hub domain identifier. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.
Level: 32

Type: TRACE

Impact: Logging

BDSS-60020: Hub User

Cause: This message string is a label that identifies a hub user ID. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.
Level: 32

Type: TRACE

Impact: Logging

BDSS-60021: SessionID

Cause: This message string is a label that identifies a user synchronization session ID. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.
Level: 32

Type: TRACE

Impact: Logging

BDSS-60022: Connector user

Cause: This message string is a label that identifies a Connector user ID. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 32

Type: TRACE

Impact: Logging

BDSS-60023: Connector Name

Cause: This message string is a label that identifies a PIM connector name. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.
Level: 32

Type: TRACE

Impact: Logging

BDSS-60024: PIM Record Identifier

Cause: This message string is a label that identifies a PIM record ID. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.
Level: 32

Type: TRACE

Impact: Logging

BDSS-60025: Version Identifier

Cause: This message string is a label that identifies a PIM record version identifier. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.
Level: 32

Type: TRACE

Impact: Logging

BDSS-65001: Could not find Exchange account information for the user.

Cause: Secure Socket Layer (SSL) handshaking failed.

Action: Ensure the Certificate Authority (CA) that issued the server certificate is installed as a trusted CA in the Web Logic Server Key Store.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65003: The following configuration is invalid. Profile = {0}. Section = {1}. Parameter {2}. Using default value {3}.

Cause: The configuration exists in the BDSS data store, but contains an invalid value.

Action: Modify the value and restart BDSS to use a value other than the default.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65004: Failed to read configuration profile. {0}.

Cause: The profile does not exist in the BDSS data store or is misspelled.

Action: Ensure the profile name is spelled correctly. Verify the case of the profile name is correct and that space characters exist where they are expected. Restart BDSS.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65005: Failed to read configuration section. Profile = {0}, Section = {1}.

Cause: The section does not exist in the specified profile in the BDSS data store or is misspelled.

Action: Ensure the section and profile names are spelled correctly. Verify the case of the profile and section name are correct and that space characters exist where they are expected. Restart BDSS.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65006: Failed to read configuration parameter. Profile = {0}, Section = {1}, Parameter = {2}.

Cause: The parameter does not exist in the specified section and profile in the BDSS data store or is misspelled.

Action: Ensure the parameter, section, and profile names are spelled correctly. Verify the case of the parameter, section and profile are correct and that space characters exist where they are expected. Restart BDSS.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65007: The domain XSD file has an invalid attribute value. XSD file {0}. Attribute Name = {1}. Attribute Value = {2}. Using default value of {3}.

Cause: The XSD for the domain has a XML attribute that contains an invalid value.

Action: Modify the specified XSD attribute and restart the connector.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65009: Failed to get a multi-valued group (MVG) field from the domain XSD. XSD file {0}. MVG Field Name = {1}.

Cause: The XSD for the domain has an invalid definition for a multi-valued group field name causing the connector to fail when parsing the XSD.

Action: Update the specified MVG field definition in the specified XSD file.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65010: Failed to add domain target for the user during session. Domain Target = {0}

Cause: The user does not have an Exchange account.

Action: Verify the user has a valid Exchange account and that the user can be discovered by the Microsoft Auto Discovery service.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65011: "The XML schema, {0}, is invalid.

Cause: The XSD does not define any valid field definitions.

Action: Add at least one field definition to the XSD and restart BDSS.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65012: Failed to get a field value from the Exchange record. Field Name = {0}.

Cause: The field contains a value that cannot be converted to a value acceptable to BDSS.

Action: Modify the field value in Exchange and synchronize the user again.
Level: 1

Type: ERROR

Impact: Data

BDSS-65013: Failed to set a Exchange record field value. Field Name = {0}. Field Value(s) = {1}.

Cause: The field contains a value that cannot be converted to a value acceptable to Exchange Web Service.

Action: Modify the value in the source Pim and attempt to synchronize the user again.
Level: 1

Type: ERROR

Impact: Data

BDSS-65014: Failed to convert a PimUpsertRecord to an Exchange {0}.

Cause: The connector could not convert a field value it received from the BDSS Engine to an equivalent Exchange Web Service form.

Action: This error occurs when the connector converts a record it receives from BDSS. Examine the log for the underlying error that is expected to have been logged prior to this error message. Take appropriate action once the underlying error has been identified.
Level: 1

Type: ERROR

Impact: Data

BDSS-65015: Failed to initialize a synchronization session for the Pim User.

Cause: If domain targets are correctly configured for each domain for the user, then this error indicates the folder manager could not begin a folder session for the synchronization session.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65016: Failed to extract the domain.

Cause: This error occurs when the connector fails to extract a domain.

Action: Examine the log for the underlying error that is expected to have been logged prior to this error message. Take appropriate action once the underlying error has been identified.
Level: 1

Type: ERROR

Impact: Data

BDSS-65017: Failed to get all the records for the domain and user.

Cause: This error occurs when the connector fails to obtain the record identifiers of all the records in Exchange for the user and domain.

Action: Examine the log for the underlying error that is expected to have been logged prior to this error message. Take appropriate action once the underlying error has been identified.
Level: 1

Type: ERROR

Impact: Data

BDSS-65018: Failed to create an Exchange record.

Cause: This error occurs when the connector fails to create an Exchange record for the user and domain.

Action: Examine the log for the underlying error that is expected to have been logged prior to this error message. Take appropriate action once the underlying error has been identified.
Level: 1

Type: ERROR

Impact: Data

BDSS-65019: Failed to update an Exchange record.

Cause: This error occurs when the connector fails to update an Exchange record for the user and domain.

Action: Examine the log for the underlying error that is expected to have been logged prior to this error message. Take appropriate action once the underlying error has been identified.
Level: 1

Type: ERROR

Impact: Data

BDSS-65020: Failed to delete an Exchange record.

Cause: This error occurs when the connector fails to delete an Exchange record for the user and domain.

Action: Examine the log for the underlying error that is expected to have been logged prior to this error message. Take appropriate action once the underlying error has been identified.
Level: 1

Type: ERROR

Impact: Data

BDSS-65021: Failed to end the synchronization session for the user.

Cause: This error occurs when the connector fails to end a synchronization session for the user.

Action: Examine the log for the underlying error that is expected to have been logged prior to this error message. Take appropriate action once the underlying error has been identified.
Level: 1

Type: ERROR

Impact: Data

BDSS-65022: Failed to create an Exchange context.

Cause: This error occurs when the connector fails to construct an internal Exchange context for the user.

Action: Examine the log for the underlying error that is expected to have been logged prior to this error message. Take appropriate action once the underlying error has been identified.
Level: 1

Type: ERROR

Impact: Data

BDSS-65023: Failed to initialize the Exchange 2007 Pim Transport.

Cause: The Pim Transport component could not be initialized.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65024: Could not obtain the folder id for Pim User {0}.

Cause: The connector could not find the folder id for the user.

Action: Verify the user has a valid domain target configuration.
Level: 1

Type: ERROR

Impact: Data

BDSS-65025: Received a error from an Exchange Web Service call. Response Code = {0}. Response message: {1}. {2}

Cause: The Exchange Web Service returned an error.

Action: Examine the response code and response message and consult Microsoft documentation regarding the error. Take appropriate action to resolve the error and synchronize the user.
Level: 1

Type: ERROR

Impact: Data

BDSS-65026: Failed to get the users Exchange server.

Cause: This error occurs when the connector cannot obtain the name of the Exchange 2007 server hosting the user's Exchange account.

Action: Verify the user has an Exchange account and that the account is discoverable by the Exchange Auto Discovery service. Consult Microsoft documentation regarding the Auto Discovery service.
Level: 1

Type: ERROR

Impact: Data

BDSS-65027: Failed to get the user's Exchange folder identifier for the domain.

Cause: The administrative user accessing the syncing users account does not have sufficient privileges.

Action: Ensure the administrative user has full mailbox rights to the syncing users mailbox.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65028: The domain is not supported.

Cause: The domain class is not supported by the Exchange 2007 connector.

Action: Specify the domain class in the XSD as one of 'TaskType', 'ContactItemType' or 'ItemType' and verify all field definitions are correct.
Level: 1

Type: ERROR

Impact: Data

BDSS-65029: Failed to get the distinguished folder identifier for the domain.

Cause: The connector could not determine the distinguished folder id for the domain.

Action: Ensure the hub domain is either 'Task', 'Contact', or 'Calendar'.
Level: 1

Type: ERROR

Impact: Data

BDSS-65030: Failed to get the item id for a record from the BDSS data store.

Cause: Accessing the Connector Runtime Library failed or the BDSS data store is not accessible.

Action: Verify the BDSS data store and the Connector Runtime Library services are both online and available and resynchronize the user.
Level: 1

Type: ERROR

Impact: Data

BDSS-65031: Failed to create or find the Exchange folder to synchronize for domain target {0}.

Cause: Invalid domain target configuration.

Action: Fix the domain target configuration for the user.
Level: 1

Type: ERROR

Impact: Data

BDSS-65032: Failed to create the Exchange folder {0}.

Cause: The Exchange Web Service method 'createFolder' returned an error when the connector attempted to create a subfolder.

Action: Examine the Exchange error and consult Microsoft Exchange Web Service documentation to resolve the error.
Level: 1

Type: ERROR

Impact: Data

BDSS-65033: Failed to get the Exchange Web Service URL for the user.

Cause: The user's Exchange Web Server URL could not be obtained.

Action: Verify the user has an Exchange account and that the account is discoverable by the Exchange Auto Discovery service. Consult Microsoft documentation regarding the Auto Discovery service.
Level: 1

Type: ERROR

Impact: Data

BDSS-65044: Configuration value is invalid and will be ignored. Profile = {0}, Section = {1}, Parameter = {2}, Value = {3}.

Cause: This warning occurs when the connector profile has invalid Active Directory 'ServerN' or Auto Discovery 'SCPN' configuration where N represents an ordinal greater than or equal to 0.

Action: Reconfigure the section(s) and restart BDSS.
Level: 1

Type: WARNING

Impact: Configuration

BDSS-65045: Failed to generate ordered list.

Cause: This error occurs when the connector fails to generate an ordered list of values in a configuration section.

Action: Verify the configuration section is configured correctly and restart BDSS.
Level: 1

Type: WARNING

Impact: Configuration

BDSS-65046: Invalid format for e-mail address. The domain is not specified.

Cause: The users Pim User Id is not recognized as a valid SMTP email address.

Action: Specify the Pim User Id as a SMTP email address. For example, user1@sample.com
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65047: There are no auto-discovery attributes available for the user.

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65048: Failed to generate Service Connection Point Url. Exception = {0}

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Configuration

BDSS-65050: Failed to get Service Connection Point URLs from Active Directory using path {0}. Exception: {1}

Cause: Active Directory does have a 'configurationNamingContext' container object, but it does not contain the appropriate 'serviceBindingInformation' or 'keywords' objects. Note that if multiple Active Directory servers are configured, this error can be ignored if other Active Directory servers are configured correctly.

Action: Consult with the Active Directory administrator to resolve the issue.
Level: 1

Type: WARNING

Impact: Configuration

BDSS-65054: Failed to create a directory context. Context Factory = {0}, Provider Url = {1}, Referral = {2}, Connect Timeout = {3}, Read Timeout = {4}, Security Principal = {5}, Secure Ldap = {6}, Client Certificate = {7}.

Cause: This error occurs if the connector cannot create an initial directory context.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65060: Failed to construct a {0} Pim XML record.

Cause: This error occurs when the connector fails to construct a Pim XML record from an Exchange record.

Action: Examine the log for the underlying error that is expected to have been logged prior to this error message. Take appropriate action once the underlying error has been identified.
Level: 1

Type: ERROR

Impact: Data

BDSS-65061: Failed to convert a Exchange {0} item to a PimUpsertRecord.

Cause: This error occurs when the connector fails to construct a PimUpsertRecord from an Exchange record.

Action: Examine the log for the underlying error that is expected to have been logged prior to this error message. Take appropriate action once the underlying error has been identified.
Level: 1

Type: ERROR

Impact: Data

BDSS-65062: Failed to create a domain class. Domain = {0}.

Cause: The connector failed to instantiate a domain class for a record.

Action: This error occurs when the domain XSD contains an invalid domain class.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65063: Failed to get the domain target for the user during session.

Cause: The connector could not obtain the user's domain target from a cache. Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65064: The extended field is incorrectly defined or is not allowed by the Exchange Web Service API. DistinguishedPropertySetId = {0}. PropertyId = {1}. PropertyName = {2}. PropertySetId = {3}. PropertyTag = {4}. PropertyType = {5}.

Cause: An extended field is defined incorrectly in the XSD.

Action: Consult Microsoft Exchange Web Service documentation for extended field definitions and fix the field definition in the XSD file and then restart BDSS.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65065: The indexed field is incorrectly defined or is not allowed by the Exchange Web Service API. FieldIndex = {0}. Dictionary URI = {1}.

Cause: An indexed field is defined incorrectly in the XSD.

Action: Consult Microsoft Exchange Web Service documentation for indexed field definitions and fix the field definition in the XSD file and then restart BDSS.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65066: The unindexed field is incorrectly defined or is not allowed by the Exchange Web Service API. FieldURI = {0}.

Cause: An unindexed field is defined incorrectly in the XSD.

Action: Consult Microsoft Exchange Web Service documentation for unindexed field definitions and fix the field definition in the XSD file and then restart BDSS.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65067: The Extract Response Batch Size configured value is too small.

Cause: A user has more records in their sync folder than what is allowed by the Extract Response Batch Size.

Action: Reconfigure the Extract Response Batch Size to be a large number such that no user has that many records in their folder.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65068: Failed to get the record metadata from EWS response message.

Cause: The Exchange record does not have a PR_LAST_MODIFICATION_TIME or PR_SOURCE_KEY value.

Action: Update or re-create the Exchange record and resynchronize the user.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65069: The domain XSD has an invalid or missing attribute. Attribute name = {0}. Attribute value = {1}.

Cause: The domain XSD contains an error.

Action: Examine the XSD file to locate the attribute name and value that is logged. Fix the XSD and restart BDSS.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65070: The XSD field definition could not be resolved to an Exchange field definition.

Cause: A extended field definition in the XSD is configured incorrectly.

Action: Consult Microsoft documentation on the PathToExtendedFieldType and Oracle documentation on field definitions for the Exchange 2007 connector and configure the field correctly.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65071: An index field name is required for indexed fields.

Cause: This error occurs when attempting to obtain a indexed field without specifying an index field name.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65072: The field definition for field {0} is invalid. It is not defined as a indexed, unindexed or extended field.

Cause: A field definition is incorrect.

Action: Fix the field definition and restart BDSS.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65073: The credential store does not contain the credential key {0}.

Cause: The specified credential key is not obtainable.

Action: Configure the credential key and resynchronize the user.
Level: 1

Type: ERROR

Impact: Security

BDSS-65074: Failed to get the credentials from the credential store. Credential key = {0}.

Cause: The specified credential key is not obtainable.

Action: Configure the credential key and resynchronize the user.
Level: 1

Type: ERROR

Impact: Security

BDSS-65075: Failed to start a folder session for the user.

Cause: At the beginning of a synchronization session, the connector creates a corresponding folder session to cache folder information for the user during the synchronization session. The connector could not start the folder session for the user.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

BDSS-65076: Failed to add a folder id to the folder session.

Cause: During a synchronization session, the connector uses a folder session to cache folder information for the user during the synchronization session. The connector could not add a folder id to the folder session for the user.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

BDSS-65077: Failed to get a folder id from the folder session.

Cause: During a synchronization session, the connector uses a folder session to cache folder information for the user during the synchronization session. The connector could not get a folder id from the folder session for the user.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

BDSS-65078: Failed getting folder information from the folder session.

Cause: During a synchronization session, the connector uses a folder session to cache folder information for the user during the synchronization session. The connector could not get a folder information from the folder session for the user.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

BDSS-65079: Failed to get the field value. Field URI = {0}.

Cause: This error occurs when the connector parses a Pim Xml record it receives from the BDSS hub.

Action: Verify the configuration for the field in the XSD is correct.
Level: 1

Type: ERROR

Impact: Other

BDSS-65080: Failed to get the calculated fields of the extracted records.

Cause: The connector could not obtain the calculated fields for each extracted record.

Action: Verify the configuration of the calculated field is correct and resynchronize the user.
Level: 1

Type: ERROR

Impact: Other

BDSS-65084: Failed to extract the domain because the BDSS-provided synchronization state is invalid. Retrying extraction using an empty synchronization state.

Cause: The synchronization state is corrupted in the BDSS store or does not apply to the domain target for the user.

Action: No action is required as the connector will reattempt synchronization using an empty synchronization state.
Level: 1

Type: NOTIFICATION

Impact: Data

BDSS-65086: Ended an existing folder session from a previous synchronization session.

Cause: A call to end a folder session at the end of a previous synchronization session unexpectedly failed.

Action: No action is required as the connector will end the existing session and create a new one.
Level: 16

Type: NOTIFICATION

Impact: Data

BDSS-65087: Failed to remove the domain information from the Url. Url = {0}

Cause: The Url may be malformed.

Action: Verify the URL is correct in Active Directory and retry synchronizing the user.
Level: 1

Type: ERROR

Impact: Data

BDSS-65088: Failed to close a output stream.

Cause: A stream object could not be closed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65089: Failed to obtain an Exchange record.

Cause: The Exchange server may have not be available.

Action: Resynchronize the user.
Level: 1

Type: ERROR

Impact: Data

BDSS-65090: The Hub Domain is not supported.

Cause: The Hub domain is not supported by the Exchange connector.

Action: Ensure the Hub domain is either 'Task', 'Contact' or 'Calendar' and restart BDSS.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65091: Attendee {0} was not resolvable in Active Directory or the syncing users Contact folder and subfolders.

Cause: There is no Active Directory or Contact record for the specified attendee.

Action: Optionally add the attendee to Active Directory or as a Contact in the synchronizing users folder.
Level: 1

Type: NOTIFICATION

Impact: Data

BDSS-65092: Attendees defined in public folders are not supported.

Cause: The specified attendee identifier is a public distribution member.

Action: Optionally remove the attendee from the calendar record.
Level: 1

Type: ERROR

Impact: Data

BDSS-65093: Failed to obtain record associated data from the BDSS Hub. Detected an exception from connector runtime library method getRecordAssociatedData. Exception message: {0}

Cause: A network error occurred.

Action: Attempt to synchronize the user again.
Level: 1

Type: ERROR

Impact: Data

BDSS-65094: Failed to obtain record associated data from the BDSS Hub for the following Pim record identifiers: {0}

Cause: The Hub failed to obtain the record associated data for the specified Pim record identifiers.

Action: Examine the Hub log file to determine the root cause of each error.
Level: 1

Type: ERROR

Impact: Data

BDSS-65096: Cannot delete the Exchange record because the record associated data for the specified Pim Record Id could not be obtained from the BDSS Hub.

Cause: Failed to obtain the record associated data for the given Pim Record Id. The BDSS store should have contained the record associated data.

Action: Perform an initial synchronization for the user or manually delete the record from the synchronizing users mailbox and perform another user synchronization.
Level: 1

Type: ERROR

Impact: Data

BDSS-65097: Failed to obtain the record associated data for a record that has been deleted from Exchange. Pim Record Id = {0}.

Cause: Failed to obtain the record associated data for the given Pim Record Id. The BDSS store should have contained the record associated data.

Action: Perform an initial synchronization for the user.
Level: 1

Type: ERROR

Impact: Data

BDSS-65099: Failed to establish a subscription for the specified user and domain.

Cause: BUGBUG

Action: BUGBUG
Level: 1

Type: ERROR

Impact: Data

BDSS-65100: Failed to obtain the specified users event associated data.

Cause: BUGBUG

Action: BUGBUG
Level: 1

Type: ERROR

Impact: Data

BDSS-65105: Failed to end a subscription for the specified user and domain.

Cause: BUGBUG

Action: BUGBUG
Level: 1

Type: ERROR

Impact: Data

BDSS-65106: Invalid XML Element in filter definition. Element name: {0}.

Cause: The XML file containing the filter definition for the domain has invalid content.

Action: Ensure the XML is correct and redeploy the connector and synchronize again.
Level: 1

Type: ERROR

Impact: Data

BDSS-65107: Invalid argument detected. The argument is not the expected type. Expected type: {0}. Parameter type: {1}.

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65108: Invalid argument detected. The argument(s), {0}, cannot be null or empty.

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65109: Invalid method invocation. The method, {0}, was unexpectedly invoked. {1}

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65110: Unable to get field definition for field. Field name: {0}

Cause: The specified field name either does not exist or is missing attributes in the domain schema XSD file or domain filter file.

Action: Update the appropriate file to contain the full definition of the field and either redploy the Exchange connector.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65111: Invalid expression. An ExistsExpression XML element contains another expression.

Cause: The domain filter file contains an expression inside an ExistsExpression element.

Action: Fix the ExistsExpression in the domain filter and redploy the Exchange connector.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65112: Invalid qualified name in the domain filter XML file. {0}

Cause: The domain filter XML file contains XML elements having an invalid qualified name.

Action: Fix the qualified name in the XML to be of the form 'XMLElementName' or 'XMLNamespaceAlias:XMLElementName'. For example, <GivenNamej> or <ns:GivenName>. Redploy the Exchange connector.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65113: Invalid stack state. {0}

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65114: Expected a {0} expression. Actual expression was {1}.

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65115: Invalid expression state. A {0} expression has invalid or missing required elements.

Cause: The domain filter XML has a incomplete expression definition.

Action: Fix the domain filter XML file and redploy the Exchange connector.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65116: A ComparisonExpression cannot be part of another ComparisonExpression or an ExistsExpression.

Cause: The domain filter XML has a ComparisonExpression containing invalid elements.

Action: Fix the domain filter XML file and redploy the Exchange connector.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65117: An invalid LogicalExpression has been detected.

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65118: There is no expression to negate.

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65119: Invalid FieldUri XML element. {0}

Cause: The domain filter XML has a invalid FieldUri element.

Action: Fix the domain filter XML file and redploy the Exchange connector.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65122: A LogicalExpression is not completed after joining expressions.

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65125: Invalid expression type encountered.

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65126: Failed to add a {0} expression to the Exchange Web Service restriction.

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65128: A ExistsExpression cannot be part of another ExistsExpression or a ComparisonExpression.

Cause: The domain filter XML has a ExistsExpression containing invalid elements.

Action: Fix the domain filter XML file and redploy the Exchange connector.
Level: 1

Type: ERROR

Impact: Configuration

BDSS-65129: Detected an invalid meeting identifier. The value is either null or has an invalid length. Identifier source: {0}. Identifier value: {1}. Identifier length: {2}

Cause: The meeting identifier provided in an ICal message is invalid.

Action: Identify and fix the record in the system that provided ICal message and resynchronize the user.
Level: 1

Type: ERROR

Impact: Data

BDSS-65131: Failed to find the identifier of an occurrence of a recurring calendar record. Occurrence date: {0}

Cause: The occurrence was moved to a day that is not within a month before or after the original day.

Action: Move the occurrence to a day within a month before or after the original day. Alternatively, delete the occurrence in Exchange and create a new record in its place.
Level: 1

Type: NOTIFICATION

Impact: Data

BDSS-65132: Failed to determine if the calendar record should be fanned or not. The update cannot be performed.

Cause: The connector could not determine if it needs to fan a recurring record.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65133: Failed to completely fan a calendar record. Attempting to rollback the changes by deleting fanned instances that were created.

Cause: The connector could not complete a fanning operation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65135: Failed to get record associated data identifiers from the BDSS data store.

Cause: Accessing the Connector Runtime Library failed or the BDSS data store is not accessible.

Action: Verify the BDSS data store and the Connector Runtime Library services are both online and available and resynchronize the user.
Level: 1

Type: ERROR

Impact: Data

BDSS-65136: Failed to get a record identifier from an Exchange record.

Cause: The Exchange record does not have a valid PR_SOURCE_KEY or BDSSFabricatedId extended property value.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65137: Failed to get a record version identifier from an Exchange record.

Cause: The Exchange record does not have a valid PR_LAST_MODIFICATION_TIME extended property value.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65138: Detected a non-fanned calendar meeting that has been regenerated by Exchange. Record identifier: {0}.

Cause: A calendar record is regenerated anytime an attendee to a meeting accepts the meeting.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

BDSS-65139: Invalid record level associated data for associated group name {0}.

Cause: The record level associated data for the specified group name is invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65140: A required record level associated data does not exist for a record. Associated group name {0}.

Cause: The record level associated data for the specified group name is not available for the record.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65141: Unable to get the record metadata from an Exchange record because the record has been deleted. Record identifier {0}.

Cause: The connector could not obtain the record and version identifiers from the Exchange record because it has been deleted.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

BDSS-65142: Failed to find an exception VEVENT with a RECURRENCE-ID of {0}.

Cause: The ICAL message provided to the connector does not have a exception VEVENT containing a RECURRENCE-ID value for the indicated date.

Action: A different connector provided the Exchange connector an invalid ICAL message. Contact the vendor of the other connector to pursue a fix.
Level: 1

Type: ERROR

Impact: Data

BDSS-65143: Failed to get a required ICAL property value from a VEVENT. ICAL property name {0}.

Cause: The ICAL message provided to the connector is missing a required ICAL field name and value.

Action: A different connector provided the Exchange connector an invalid ICAL message. Contact the other connector owner to pursue a fix.
Level: 1

Type: ERROR

Impact: Data

BDSS-65144: Failed to get the record level associated data for a fanned record occurring on {0}.

Cause: The connector could not obtain the record metadata for a record that has been fanned.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65145: Detected more than two Exchange records having the same meeting identifier. Meeting identifier: {0}

Cause: The connector detected more than two calendar records having the same meeting identifier.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65146: Detected an Exchange record without a meeting identifier.

Cause: The connector detected a calendar record in Exchange that does not have a meeting identifier.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65146: A calendar extraction contained two records having the same meeting identifier. The connector failed to determine which of the two records is the original. Meeting identifier: {0}

Cause: The connector failed to get the record identifier or associated data for an Exchange regenerated meeting.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65147: Detected a fanned calendar meeting that has been regenerated by Exchange. Record identifier: {0}.

Cause: A calendar record is regenerated anytime an attendee to a meeting accepts the meeting.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

BDSS-65148: Failed to coalesce fanned records containing meeting occurrences that have been regenerated by Exchange. Record identifier: {0}.

Cause: The connector failed to located which fanned instances of a recurring meeting were regenerated by Exchange.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65149: Failed to coalesce fanned records. A fanned instance has an invalid meeting identifier. Record identifier: {0}. Meeting identifier: {1}.

Cause: The connector failed to coalesce fanned calendar instances because the meeting identifiers are not valid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65150: Failed to coalesce fanned records into a single record because of an invalid record count. Record identifier: {0}. Meeting identifier: {1}. Expected count: {2}. Actual count: {3}

Cause: The connector failed to coalesce fanned calendar instances because it does not have the expected number of fanned occurrences.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65151: Failed to coalesce fanned records to a single delete because of an invalid record count. Record identifier: {0}. Expected count: {1}. Actual count: {2}

Cause: The connector failed to coalesce fanned calendar instances because it does not have the expected number of fanned occurrences.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65152: Failed to coalesce fanned records to a single record because of an invalid record fanning metadata. Record identifier: {0}.

Cause: The connector failed to coalesce fanned calendar instances because the fanning state is invalid for a transition from a unsupported to supported recurrence pattern.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65153: Failed to coalesce fanned records to a single record because of invalid record level associated data. Record identifier: {0}.

Cause: The record level associated data has a null or empty meeting identifier or Exchange record identifier for the fanned instance.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65154: Failed to save record level associated data to the BDSS store.

Cause: The runtime library returned an error when attempting to save record-level associated data.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65155: Failed to get master VEvent from associated data.

Cause: Unable to get the master VEvent data from record-level associated data.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65156: Invalid Exchange record item identifier detected.

Cause: An Exchange record did not have a valid item identifier.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65157: Invalid Exchange record item detected.

Cause: An Exchange record did not have a valid item type.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65158: Invalid record version identifier from the BDSS data store. Record identifier: {0}.

Cause: BDSS provided an invalid version identifier for a record.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65159: Invalid record identifier from the BDSS data store.

Cause: BDSS provided an invalid record identifier.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

BDSS-65160: An unexpected error occurred in the connector while synchronizing the specified domain. Synchronization cannot complete.

Cause: The specified user is being synchronized in multiple sessions or the connector could not allocate a required resource.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

7 CLONE-27010 to CLONE-28400

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

8 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-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-09042: MetadataManager cannot return the measure dimension.

Cause: Invalid or corrupt metadata was found in the database.

Action: Repair problems with or rebuild the database schema.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-09511: illegal pivot operation

Cause: Dimensions or locations were provided that would not result in a legal pivot operation.

Action: Check the given arguments and reconcile them with the layout of the current query.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-09512: illegal swap operation

Cause: Dimensions or locations were provided that would not result in a legal swap operation.

Action: Check the given arguments and reconcile them with the layout of the current query.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-09513: illegal swap edges operation

Cause: Edges were provided that would not result in a legal swap operation.

Action: Check the given edges and reconcile them with the layout of the current query.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-09515: No query is defined.

Cause: A method was called that requires an existing query.

Action: Create a query before calling the method.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-09532: The specified dimension or item is invalid: {0}.

Cause: A dimension or item name was specified that cannot be found in the current database.

Action: Ensure that all named dimensions or items are in the current database.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10000: Event is not consumable.

Cause: An attempt was made to consume an event that is not consumable.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10101: Handler fails to handle UserObject.

Cause: A failed attempt was made to bind or look up an object whose state could not be set or retrieved.

Action: Check the underlying error stack to find the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10105: BISession is not specified.

Cause: An instance of BISession was not set on the MetadataManager object.

Action: Set a BISession on the MetadataManager object, using the setSession method.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10107: User cannot set the specified property: {0}.

Cause: An attempt was made to set a property other than Label on an MDObject.

Action: Ensure that only the Label property is set on the MDObject.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10108: MetadataManager cannot disconnect the connection.

Cause: MetadataManager could not disconnect the connection.

Action: Check the underlying error stack to find the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10109: MetadataManager cannot free the connection.

Cause: The MetadataManager could not release the connection.

Action: Check the underlying error stack to find the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10110: MetadataManager cannot retrieve the OracleConnection.

Cause: The MetadataManager could not retrieve the OracleConnection.

Action: Check the underlying error stack to find the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10300: cannot bind a context

Cause: An attempt was made to save a folder using the bind method.

Action: To create a new folder, use the createSubcontext method. To copy a folder to another folder, use the copy method. To move a folder to another folder, use the move method.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10301: The specified attribute is not valid.

Cause: The key or the value of one or more attributes in the method was not valid.

Action: Specify a valid attribute key and value.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10302: Name {0} is invalid; the name must not be an empty string.

Cause: The specified name was not valid. For any methods of BIContext that require a name argument, the user cannot specify a null value. The following methods also require that the name argument not be an empty string: bind, rebind, createSubcontext, destroySubcontext, rename and unbind.

Action: Specify a name whose value is not an empty string.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10303: The specified object is invalid.

Cause: An attempt was made to save a UserObject that contains an object that is not accepted by the specific driver.

Action: Set the appropriate object in UserObject for the specified driver type.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10304: The specified search control is invalid.

Cause: The specified search control was not valid for one of the following reasons: The search scope was not valid. It must be one of the following: OBJECT_SCOPE, ONELEVEL_SCOPE, SUBTREE_SCOPE, ONELEVEL_SCOPE_WITH_FOLDERS, or SELECTIVE_ONELEVEL_SCOPE. The specified time limit was a negative number. The specified count limit was a negative number.

Action: Review the possible reasons and take the appropriate action.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10305: Object with name {0} already exists.

Cause: An attempt was made to save an object with a name that was already bound to an object in the storage system, or the destination folder already contained an object that was bound to that particular name when the copy or move operation was performed.

Action: If this is a save operation, then use the rebind method to overwrite the existing object that is bound with that name. If this is a copy operation, then specify a different target name.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10306: Object with name {0} cannot be found.

Cause: An attempt was made to retrieve, copy, or move an object that does not exist.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10307: User lacks sufficient privileges to perform the operation.

Cause: An attempt was made to perform an operation that requires specific privileges, for example, saving an object to a folder in which the user does not have write access.

Action: Request that the owner or user of the folder with full-control privileges assign sufficient privileges to the appropriate user to perform the operation.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10308: The object is not a valid context.

Cause: Depending on the operation, this error could occur because: The destination folder for copy or move operations was not a valid folder. The name argument in list, listBindings, or search operations did not resolve to a folder.

Action: Specify a valid folder name.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10309: This operation is not supported.

Cause: The operation was not supported by the driver in which the operation was invoked.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10310: unknown exception

Cause: An unknown error occurred.

Action: Check the underlying error stack to find the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10311: error while adding, removing, or modifying attributes

Cause: An error has occurred while performing the modifyAttributes operation.

Action: Check the underlying error stack to find the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10313: A circular reference is detected.

Cause: The operation attempted to use aggregated, copied, or moved objects that cause a circular reference.

Action: If this is a bind or rebind operation, then ensure that no circular reference exists in the aggregate tree. If this is a copy or move operation on a folder, then ensure that the parent folder is not copied or moved to the subfolder.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10315: The specified folder path is invalid.

Cause: An attempt was made to save an object in a folder path that does not exist.

Action: Specify a valid folder path.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10500: MetadataManager driver cannot be instantiated.

Cause: A failure occurred while creating an instance of the MetadataManager driver. The failure can happen only if the MetadataManager drivers are interfaces or are abstract classes.

Action: Check the underlying error stack to find the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10501: illegal attempt to access the MetadataManager driver

Cause: A failure occurred while creating an instance of the MetadataManager driver. The failure can happen only if the MetadataManager drivers are not public or are not in the MetadataManager package.

Action: Check the underlying error stack to find the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10502: MetadataManager driver is not found.

Cause: A failure occurred while creating an instance of the MetadataManager driver. The failure can happen only if the necessary jar files are not referenced in the CLASSPATH setting.

Action: Ensure that all necessary classes are included in the CLASSPATH setting.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10503: User cannot set the specified property: {0}.

Cause: An attempt was made to set a property other than Label on the MeasureDimension MDObject.

Action: Ensure that only the Label property is set on the MeasureDimension MDObject.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-10504: MetadataManager cannot retrieve the OracleConnection.

Cause: The MetadataManager could not retrieve the OracleConnection.

Action: Check the underlying error stack to find the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-12000: unexpected error

Cause: An unknown exception occurred in a call to a different class.

Action: Check the underlying error stack to find the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-16001: BISession is not specified.

Cause: An instance of BISession was not set on the Connection object.

Action: Set a BISession on the Connection object using the setSession method.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-16002: Operation is incomplete because there is no database connection.

Cause: The connection was not initialized.

Action: Invoke the connect method before performing this operation.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-16003: cannot set the connection object because a connection already exists

Cause: Could not set the connection object because a connection already exists.

Action: Disconnect and set the connection object again.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-16004: The operation cannot complete because the object retrieved is a nonserializable object.

Cause: The operation was not completed because the retrieved object was not serializable.

Action: Retrieve an object only if it does not require serialization.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-16400: Connection driver cannot be instantiated.

Cause: A failure occurred while creating an instance of the Connection driver. The failure can happen only if the Connection drivers are interfaces or abstract classes.

Action: Check the underlying error stack to find the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-16401: illegal attempt to access the Connection driver

Cause: A failure occurred while creating an instance of the Connection driver. The failure can happen only if the Connection drivers are not public or are not in the Connection package.

Action: Check the underlying error stack to find the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-16402: Connection driver is not found.

Cause: A failure occurred while creating an instance of the Connection driver. The failure can happen if the necessary jar files are not referenced in the CLASSPATH setting.

Action: Ensure that all necessary classes are included in the CLASSPATH setting.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-18008: No QueryContext is defined.

Cause: A method was called that requires an existing QueryContext object.

Action: Create a QueryContext object before calling the method.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-18009: No Selection is defined.

Cause: A method was called that requires an existing Selection object.

Action: Create a Selection object before calling the method.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-18010: The QueryAccess object cannot be created.

Cause: A QueryAccess object could not be created.

Action: Verify that a valid QueryContext object exists. To create a QueryAccess object, use syntax such as queryContext.createQueryAccess.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-18011: A DataAccess object cannot be created.

Cause: A DataAccess object could not be created.

Action: Verify that a valid QueryAccess object exists and that the dimension that is specified for the Selection is valid.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-18012: unexpected error

Cause: An unknown exception occurred in a call to a different class.

Action: Check the underlying error stack to find the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

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

9 HELP-00001 to HELP-30008

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

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

11 MDS-00001 to MDS-91023

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-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 using local reference(s) : "{0}" 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-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} 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-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-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-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-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-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-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-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-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-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-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-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-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, or IBMDB2. "{0}" operation failure.

Cause: dbVendor value was not correct.

Action: Ensure the dbVendor value is one of ORACLE, MSSQL, or IBMDB2.
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

12 RCS-00001 to RCS-23000

RCS-00001: unexpected error has occurred

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-00002: unexpected error has occurred

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-00003: failed to instantiate an instance of class [{0}]

Cause: The class could be found in the classpath

Action: Ensure the class is included in the application classpath
Level: 1

Type: ERROR

Impact: Programmatic

RCS-00004: required parameter [{0}] is missing or null

Cause: An attempt was made to invoke a method without passing all the required parameters

Action: Ensure all required parameters are passed to the method
Level: 1

Type: ERROR

Impact: Programmatic

RCS-00005: cannot find resource bundle [{0}]

Cause: The resource bundle could not be found on the classpath

Action: Ensure the resource bundle is included in the application classpath
Level: 1

Type: ERROR

Impact: Configuration

RCS-00006: cannot find resource [{1}] in resource bundle [{0}]

Cause: An attempt was made to load a text resource from a resource bundle but the resource was not found. The resource key was used instead.

Action: Add the missing resource to the resource bundle or correct the resource reference.
Level: 1

Type: ERROR

Impact: Programmatic

RCS-00007: value [{1}] for parameter [{0}] is invalid

Cause: An invalid parameter value was passed to the method

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00008: expected type [{1}] but received type [{2}] for parameter [{0}]

Cause: An attempt was made to read a parameter value but the parameter type was invalid

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00009: operation [{0}] is not supported in this release

Cause: An attempt was made to invoke a method that is not supported in this release

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00010: name [{0}] is not valid for a resource catalog object

Cause: An attempt was made to access a resource catalog object using a name that does not conform to the required structure or format

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00011: no objects bound to name [{0}]

Cause: An attempt was made to find an object using the specified name. No object was bound to that name.

Action: Verify that the named object has not been renamed or deleted and re-try the operation.
Level: 1

Type: ERROR

Impact: Logging

RCS-00012: error while initializing class

Cause: An unexpected error occurred during execution of a static initializer while loading a Java class. The class could not be loaded

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00013: invalid MDS reference [{0}]

Cause: An attempt was made to create an MDS Reference from a String that does not conform to the required format

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00014: error while flushing pending changes for RCSession [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-00015: error while canceling pending changes for RCSession [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-00016: error while creating a URI using catalog Id [{0}] and catalog path [{1}]

Cause: The catalog id or catalog path contain characters that are invalid in a URI

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00017: error [{1}] while creating a catalog reference from URI [{0}]

Cause: The specified URI could not be parsed either because it is not a Catalog Reference URI or the URI is corrupt

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00018: error while creating a URI using repository [{0}] and repository path [{1}]

Cause: The repository id or repository path contain characters that are invalid in a URI

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00019: error while creating a repository reference from URI [{0}]

Cause: The specified URI could not be parsed either because it is not a repository reference URI or the URI is corrupt

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00020: data type [{1}] in attribute descriptor [{0}] is not supported

Cause: An attempt was made to create an attribute descriptor using an invalid data type

Action: Change the attribute descriptor to use a supported data type.
Level: 1

Type: ERROR

Impact: Programmatic

RCS-00021: error [{0}] while setting default value [{2}] on attribute descriptor [{1}]

Cause: Review the cause included in the message for more details

Action: Take appropriate action based on the cause included in the message and any underlying exceptions
Level: 1

Type: ERROR

Impact: Programmatic

RCS-00022: Session properties cannot be modified after the session has been initialized.

Cause: An attempt was made to modify the properties of a resource catalog session after the session had been initialized

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00023: operation [{0}] is not allowed in the current session

Cause: An attempt was made to perform a catalog related operation in a session configured for connection operations only

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00026: operation canceled. operation=[{0}]. reason=[{1}]

Cause: An operation was canceled by a user. This usually happens when the operation was taking too long to complete.

Action: No action is necessary
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-00027: search canceled. root context=[{0}]. expression=[{1}]. reason=[{2}]

Cause: A search operation was canceled by a user because it may have taken too long to complete

Action: No action is necessary
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-00028: Error attempting to modify an immutable object

Cause: A client program attempted to modify a immutable object

Action: Correct the client so it does not attempt to modify immutable objects
Level: 1

Type: ERROR

Impact: Programmatic

RCS-00029: operation [{0}] is not supported in a Web application. Commit all changes via ADFContext

Cause: An attempt was made to invoke a method that is not supported in a web application

Action: Use ADFContext to commit changes to MDS or connections
Level: 1

Type: WARNING

Impact: Programmatic

RCS-00030: Catalog element id [{0}] contains invalid characters. Use a-z, A-Z, 0-9, _ and .

Cause: Invalid characters were detected in a catalog element ID while attempting to add the element to a catalog

Action: Use IDs that contain only the allowable characters
Level: 1

Type: WARNING

Impact: Programmatic

RCS-00031: Catalog element id [{0}] is not unique in catalog [{1}]

Cause: I to add the element to a catalog

Action: Use an ID that is unique within the scope of the catalog definition
Level: 1

Type: WARNING

Impact: Programmatic

RCS-01000: The resource catalog service has not been configured for this application.

Cause: Configuration parameters for the resource catalog service could not be found in the application's adf-config.xml file

Action: Refer to the resource catalog service documentation and add the necessary configuration parameters to the application's adf-config.xml file
Level: 1

Type: ERROR

Impact: Configuration

RCS-01001: configuration parameter [{1}] is missing from resource catalog instance [{0}]

Cause: A required configuration parameter was not specified in the adf-config.xml file.

Action: Refer to the resource catalog service documentation and add the missing configuration parameter to the configuration file
Level: 1

Type: ERROR

Impact: Configuration

RCS-01002: Invalid configuration parameter. RCInstance=[{0}] Parameter=[{1}] Invalid value=[{2}] Substituted value=[{3}]

Cause: The resource catalog service was configured with an invalid parameter value

Action: Refer to the resource catalog service documentation and correct the configuration parameters
Level: 1

Type: ERROR

Impact: Configuration

RCS-01003: error occurred initializing MDS instance [{0}]

Cause: The MDS instance used by the resource catalog service could not be initialized due to an previous error

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

RCS-01004: a resource catalog instance with Id [{0}] already exists.

Cause: An attempt was made to create a new resource catalog instance using an ID that is already in use by another instance.

Action: Verify that the instance Id specified in adf-config.xml is unique. If it is unique, verify that the application code is not attempting to create multiple instances with the same ID instead of re-using an existing instance.
Level: 1

Type: ERROR

Impact: Configuration

RCS-01005: error while obtaining a connection context using connection context provider [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01006: error while obtaining an MDS Session from session provider [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01007: an ADFContext has not been registered for name [{0}].

Cause: The named ADFContext required by the resource catalog service cannot be found

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01008: error while initializing the connections context

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01009: error while creating a connections metadata object using path [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-01010: error while deleting a connections metadata object using path [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-01011: error while opening a connections metadata object using path [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-01012: error while attempting to locate the resource catalog extensions.

Cause: An exception was raised while attempting to find resource catalog extensions from the classpath

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01013: cannot find any resource catalog extensions on the classpath

Cause: The classpath did not include any jars that declare resource catalog extensions. The resource catalog requires at least one connection type and one resource catalog adapter to function.

Action: Add one or more jar files containing these extensions to your application classpath
Level: 1

Type: WARNING

Impact: Configuration

RCS-01014: error while processing a resource catalog extension using URL [{0}]

Cause: An exception was raised while loading a resource catalog extension. Failure to load one extension does not prevent other extensions from loading

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01015: error while instantiating CatalogItemFactoryPlugin [{0}]

Cause: The specified plugin could not be instantiated or does not implement the required interface. Failure to load one plugin does not prevent the loading of others.

Action: Add the missing class to the classpath, modify the class to implement the correct interface or remove the declaration from META-INF/rc_ext.xml
Level: 1

Type: ERROR

Impact: Configuration

RCS-01016: error while instantiating a resource type [{0}]

Cause: The specified plugin class could not be instantiated or does not implement the required interface. Failure to load one plugin does not prevent the loading of others.

Action: Add the missing class to the classpath, modify the class to implement the correct interface or remove the declaration from META-INF/rc_ext.xml
Level: 1

Type: ERROR

Impact: Configuration

RCS-01017: duplicate resource type [{0}]

Cause: A Resource Type with the specified ID has already been loaded. The duplicate was ignored

Action: Remove the declaration for the duplicate resource type from META-INF/rc_ext.xml
Level: 1

Type: WARNING

Impact: Configuration

RCS-01019: Target directory [{0}] for resource catalog configuration files does not exist.

Cause: An attempt was made to dynamically create a resource catalog instance, but the target directory specified by the client does not exist.

Action: Create the target directory or configure the client to use a different directory for the resource catalog configuration files
Level: 1

Type: ERROR

Impact: Configuration

RCS-01020: Target path [{0}] for resource catalog configuration files is not valid.

Cause: An attempt was made to dynamically create a resource catalog instance, but the target path specified by the client is not a directory

Action: Configure the client to use a different path for the resource catalog configuration files. The path must be a directory
Level: 1

Type: ERROR

Impact: Configuration

RCS-01021: Target directory [{0}] for resource catalog configuration files is not readable.

Cause: An attempt was made to dynamically create a resource catalog instance, but the target directory specified by the client is not readable

Action: Change the permissions on the target directory so it is readable or configure the client to use a different path for the resource catalog configuration files.
Level: 1

Type: ERROR

Impact: Configuration

RCS-01022: Target directory [{0}] for resource catalog configuration files is not writable.

Cause: An attempt was made to dynamically create a resource catalog instance, but the target directory specified by the client is not writable

Action: Change the permissions on the target directory so it is writable or configure the client to use a different path for the resource catalog configuration files.
Level: 1

Type: ERROR

Impact: Configuration

RCS-01023: An ADFContext has already been registered using name [{0}].

Cause: The named ADFContext required by the resource catalog Service cannot be registered using the specified name because the name is already in use

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01024: error while creating a resource catalog instance

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01025: cannot find configuration template [{0}]

Cause: The specified configuration file template could not be found on the application classpath

Action: Ensure the missing template is included in the classpath
Level: 1

Type: ERROR

Impact: Configuration

RCS-01026: error occurred initializing the resource catalog security manager

Cause: An exception was raised while initializing the resource catalog security manager

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01027: error occurred creating directory {0}"

Cause: An attempt to create a directory for the resource catalog configuration files failed

Action: Change the permissions on the directories in the path so they are writable or configure the client to use a different path for the resource catalog configuration files.
Level: 1

Type: ERROR

Impact: Configuration

RCS-01028: error occurred creating configuration file {0}"

Cause: An attempt to create a resource catalog configuration file failed

Action: Change the permissions on the directories in the path so they are writable or configure the client to use a different path for the resource catalog configuration files.
Level: 1

Type: ERROR

Impact: Configuration

RCS-01029: default resource library for catalog editing is not configured

Cause: An attempt was made to open the default resource library for catalogs, but a resource library has not been configured in adf-config.xml

Action: configure the default resource library in adf-config.xml
Level: 1

Type: WARNING

Impact: Configuration

RCS-01030: default resource library for navigation model editing is not configured

Cause: An attempt was made to open the default resource library for navigation models, but a resource library has not been configured in adf-config.xml

Action: configure the default resource library in adf-config.xml
Level: 1

Type: WARNING

Impact: Configuration

RCS-01031: The value of system property oracle.adf.rc.classpathcontext.expires must be numeric.

Cause: The system property has been specified, but the value is not numeric

Action: Change the value ot the system property to a numeric value or remove it.
Level: 1

Type: WARNING

Impact: Configuration

RCS-02000: error while attempting to lookup connection [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-02001: cannot find connection [{0}]

Cause: The specified connection could not be found. The connection may have been deleted or renamed

Action: Create a new connection with the specified ID
Level: 1

Type: ERROR

Impact: Configuration

RCS-02003: error while registering resource catalog adapter factory [{1}] for connection type [{0}]

Cause: An exception was raised while registering the resource catalog adapter

Action: Verify the connection type registered and that the resource catalog adapter factory class is included in the application classpath
Level: 1

Type: ERROR

Impact: Logging

RCS-02004: A resource catalog adapter has already been registered for connection type [{0}]. The duplicate will be ignored

Cause: Two or more META-INF/rc_ext.xml files found on the application classpath include resource catalog adapter declarations for the same connection type.

Action: Remove the duplicate adapter declarations from the application classpath
Level: 1

Type: WARNING

Impact: Logging

RCS-02005: The resource catalog adapter factory [{1}] for connection type [{0}] does not implement the required interfaces.

Cause: Resource catalog adapters are required to implemented a specific set of interfaces. The specified adapter does not implement one or more of these interfaces.

Action: If the adapter was provided by Oracle, contact Oracle Support Services. Otherwise contact the provider of the adapter
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-02006: cannot find a resource catalog adapter for connection type [{0}]

Cause: A resource catalog adapter has not been registered for the specified connection type.

Action: Add an appropriate resource catalog adapter implementation to the application classpath
Level: 1

Type: ERROR

Impact: Logging

RCS-02009: error while creating InitialContext for repository ID [{0}], repository path [{1}] using InitialContextFactory [{2}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-02010: error while closing subcontext [{0}] for repository id [{1}], repository path [{2}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-02011: cannot find resource catalog environment parameter [{0}]

Cause: An expected parameter could not be found in the resource catalog environment hashtable

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-02012: The value [{1}] of resource catalog environment parameter [{0}] is not valid.

Cause: An attempt was made to read a resource catalog environment variable but the variable contained an invalid value.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-02013: error while obtaining the connection type for connection [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-02014: resource catalog adapter factory [{0}] returned null for repository reference [{1}]

Cause: The resource catalog adapter factory returned null when a CatalogContext object was expected.

Action: If the resource catalog adapter was provided by Oracle, contact Oracle Support Services. Otherwise contact the provider of the adapter
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-02015: unexpected object type [{1}] returned by resource catalog adapter factory [{0}] for repository reference [{2}]

Cause: The resource catalog adapter factory returned an invalid object type. Adapter factories are required to return an instance or oracle.adf.rc.core.CatalogContext.

Action: If the InitialContextFactory was provided by Oracle, contact Oracle Support Services. Otherwise contact the provider of the InitialContextFactory
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-02016: cannot find connection type for connection [{0}]

Cause: The resource catalog service could not determine the connection type of the specified connection.

Action: Declare the connection type in META-INF/rc_ext.xml (runtime) or META-INF/extension.xml (designtime).
Level: 1

Type: WARNING

Impact: Programmatic

RCS-02017: error while creating InitialContext for repository ID [{0}], repository path [{1}] using InitialContextFactory [{2}]. Error was [{3}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-02018: error while registering custom folder factory [{1}]

Cause: An exception was raised while registering the custom folder

Action: Verify the custom folder factory class is included in the application classpath
Level: 1

Type: WARNING

Impact: Logging

RCS-03000: cannot find resource catalog using MDS reference {0}

Cause: An attempt was made to open a resource catalog, but the catalog could not be found

Action: Verify the catalog exists in the MDS repository. If the document exists, check the resource catalog configuration settings in adf-config.xml
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03001: catalog with MDS reference {0} already exists

Cause: A resource catalog with the specified MDS reference already exists.

Action: Open the existing catalog or choose a different MDS reference if you want to create a new catalog.
Level: 1

Type: WARNING

Impact: Logging

RCS-03002: MDS reference {0} is not valid

Cause: The MDS reference generated using the specified scope and id was rejected by MDS

Action: Use an ID whose structure and characters meets the requirements for MDS references.
Level: 1

Type: ERROR

Impact: Logging

RCS-03003: error while renaming catalog from [{0}] to [{1}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03005: error while deleting resource catalog [{0}] using MDS Path [{1}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03008: error while removing element [{1}] from resource catalog [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03010: error while adding element [{1}] to parent element [{2}] in resource catalog [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03011: error while processing an elementAdded event for element [{3}], folder [{2}] in resource catalog [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03012: error while processing an elementModified event for element [{3}], folder [{2}] in resource catalog [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03013: error while processing an elementRenamed event, renaming element [{2}] to [{3}] in folder [{1}], resource catalog [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03014: unrecognized element [{1}:{2}] found in resource catalog [{0}]

Cause: The resource catalog definition contains an unrecognized element type. The element was ignored.

Action: Remove the invalid element from the resource catalog definition
Level: 1

Type: WARNING

Impact: Logging

RCS-03015: Element [{1}] of resource catalog [{0}] has been excluded from the catalog due to error [{2}].

Cause: An exception was raised by an underlying component that prevented the specified element from being included in the catalog.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03016: An error has occurred while creating folder [{1}] in resource catalog [{0}]. The folder was ignored.

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03017: An error has occurred while creating dynamic folder [{1}] in resource catalog [{0}]. The dynamic folder was ignored.

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03018: An error has occurred while processing expression filter [{2}] of folder [{1}] in resource catalog [{0}]. The filter was ignored.

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03019: An error has occurred while creating custom filter [{2}] of folder [{1}] in resource catalog [{0}]. The folder was ignored. Filter class=[{3}].

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03020: An error has occurred while creating custom folder [{1}] in resource catalog [{0}]. The custom folder was ignored. Factory class=[{2}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03021: cannot find resource using repository [{0}] and repository path [{1}]. The repository may not be accessible or the resource may have been deleted or renamed

Cause: The source repository may be temporarily inaccessible or the resource may have been deleted or renamed in the source repository.

Action: Refresh the parent folder see the revised contents
Level: 1

Type: WARNING

Impact: Logging

RCS-03022: unexpected object type returned using repository [{3}] and repository path [{4}] in resource catalog [{0}]. Expected [{1}] but received [{2}] from adapter [{5}]

Cause: A resource catalog adapter returned an unexpected item type

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03023: An error has occurred while querying source repository [{2}], repository path [{3}] for dynamic folder [{1}] in resource catalog [{0}]. The dynamic folder source was ignored

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03024: The custom content element [{1}] in resource catalog [{0}] does not specify a CustomContextProvider class. The element was ignored.

Cause: The specified custom content element does not include a class attribute specifying the CustomContentProvider implementation. This attribute is required.

Action: Add the missing attribute to the specified element or remove it from the catalog.
Level: 1

Type: ERROR

Impact: Logging

RCS-03025: Class [{2}], referenced by CustomContent element [{1}] in model [{0}], is not a CustomContentProvider

Cause: CustomContent elements must implement either CustomContentProvider or CustomContentProviderV2

Action: Update the specified element to reference a valid provider or remove the element from the definition
Level: 1

Type: ERROR

Impact: Logging

RCS-03026: An error has occurred while instantiating catalog definition filter [{1}] in resource catalog [{0}]. The filter was ignored.

Cause: The specified class could not be found in the application classpath.

Action: Verify the specified class is included in the application classpath.
Level: 1

Type: ERROR

Impact: Logging

RCS-03027: The catalog definition filter [{1}] in resource catalog [{0}] does not implement the oracle.adf.rc.spi.plugin.catalog.CatalogDefinitionFilter interface. The filter was ignored

Cause: The specified filter class does not implement the required interface.

Action: Modify the specified class so it implements the required interface or replace it with one that does.
Level: 1

Type: ERROR

Impact: Logging

RCS-03028: An error has occurred while invoking catalog definition filter [{2}] in resource catalog [{0}]. The filter was ignored.

Cause: An exception was raised by the catalog definition filter

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03029: An error has occurred while creating a custom folder using InitialContextFactory [{1}] in resource catalog [{0}]. The custom folder was ignored.

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03030: An error has occurred while refreshing the contents of folder [{1}] in catalog [{0}]. Some child elements may not have been loaded.

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03031: An error has occurred while creating catalog item [{1}] in catalog [{0}]. The catalog item was ignored.

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03032: error while adding a transient catalog element to a persistent catalog folder.

Cause: Transient catalog elements can only be added to catalogs by CustomContentProviders. They cannot be added to persistent catalog definitions.

Action: Change the client code that is invoking the specified API so it uses PersistentElements instead of TransientElements.
Level: 1

Type: ERROR

Impact: Programmatic

RCS-03033: operation [{1}] of interface [{0}] is not supported for transient elements.

Cause: An attempt was made to invoke an unsupported operation on a transient catalog element.

Action: Change the client code that it does not invoke the specified method.
Level: 1

Type: ERROR

Impact: Programmatic

RCS-03034: An attempt was made to add a persistent catalog element to a transient catalog folder.

Cause: Transient catalog folders are intended for use by CustomContentProviders. They can only contain other transient elements

Action: Change the client code so it uses TransientElements instead of PersistentElements
Level: 1

Type: ERROR

Impact: Programmatic

RCS-03035: cannot resolve reference to repository using repository [{2}], repository path [{3}] at element [{1}] in catalog [{0}]

Cause: The specified repository element could not be resolved because the repository or repository path could not be found.

Action: Verify that the catalog entry is correct, the repository exists in your application and the repository path is valid.
Level: 1

Type: ERROR

Impact: Logging

RCS-03036: cannot resolve reference to resource using repository [{2}], repository path [{3}] at element [{1}] in catalog [{0}]

Cause: The specified resource element could not be resolved because the repository or repository path could not be found.

Action: Verify that the catalog entry is correct, the repository exists in your application and the repository path is valid.
Level: 1

Type: ERROR

Impact: Logging

RCS-03037: error while opening catalog [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03038: error creating component [{1}] in resource catalog [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03039: error including catalog [{1}] in catalog [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03040: error aumenting attributes or parameters for item [{1}] in resource catalog [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03041: Parameter {0} is missing from the environment hashtable.

Cause: An expected parameter is missing or null. This usually occurs in adapter unit tests that do not correctly configure the environment hashtable

Action: Call RCAdapterManager.createEnv() or RCAdapterManager.augmentEnv() to correctly prepare the environment hashtable.
Level: 1

Type: WARNING

Impact: Logging

RCS-03042: attempt to cache a null value for item [{1}] in catalog [{0}]

Cause: An attempt was made to cache a null value in a catalog folder.

Action: Review the exception details to determine the underlying cause.
Level: 1

Type: WARNING

Impact: Logging

RCS-03043: Unable to obtain an ELContextProvider for EL expression evaluation

Cause: This error occurs when attempting to use EL expressions in an application that does not use JSF and has not been configured with an ELContextProvider

Action: Configure the RCS with a suitable ELContextProvider or remove EL expressions from your catalog definitions.
Level: 1

Type: WARNING

Impact: Logging

RCS-03044: Error resolving an EL expression. An ELContext cannot be obtained

Cause: This error may occur when attempting to use EL expressions in an application that does not use JSF or if the configured ELContextProvider returns an error.

Action: If using EL expressions outside of a Faces environment, you need to provide a suitable ELContextProvider in the RCS configuration in adf-config.xml
Level: 1

Type: WARNING

Impact: Logging

RCS-03045: Error attempting to reference FacesContext

Cause: This error occurs when attempting to use EL expressions in an application that does not use JSF

Action: If using EL expressions outside of a Faces environment, you need to provide a suitable ELContextProvider in the RCS configuration in adf-config.xml
Level: 1

Type: WARNING

Impact: Logging

RCS-03046: cannot resolve [{0}] as an EL expression

Cause: This error occurs when attempting to resolve a string that is not an EL expression

Action: Check the string is an EL expression before attempting to resolve using ELHelper
Level: 1

Type: WARNING

Impact: Programmatic

RCS-03047: Error resolving EL expression [{0}]

Cause: The EL resolution process resulted in an error

Action: Review related exception messages for the root cause.
Level: 1

Type: WARNING

Impact: Logging

RCS-03048: error creating an instance of [{2}], referenced by CustomContent element [{1}] in resource catalog [{0}]

Cause: The specified class could not be found in the application classpath.

Action: Add the specified class to the application classpath.
Level: 1

Type: ERROR

Impact: Logging

RCS-03049: CustomContentProvider [{2}], referenced by CustomContent element [{1}] is not supported in navigation model [{0}]

Cause: The CustomContentProvider interface is not supported in navigation models

Action: Change your implementation to use oracle.adf.rc.spi.plugin.catalog.CustomContentProviderV2
Level: 1

Type: ERROR

Impact: Logging

RCS-03050: error while wrapping resource [{1}] of type [{2}] in catalog [{0}]

Cause: An error occurred while wrapping a resource, component or URL element

Action: Review related exceptions for more information
Level: 1

Type: ERROR

Impact: Logging

RCS-03051: error inserting element {0} before element {1}. Element {1} not found.

Cause: While attempting to insert a new element relative to a specified element, the specified element could not be found.

Action: Verify the specified element exists in the target folder
Level: 1

Type: ERROR

Impact: Programmatic

RCS-03052: error inserting element {0} after element {1}. Element {1} not found.

Cause: While attempting to insert a new element relative to a specified element, the specified element could not be found.

Action: Verify the specified element exists in the target folder
Level: 1

Type: ERROR

Impact: Programmatic

RCS-03053: cannot merge children of element {1} in catalog {0} with a CatalogContext

Cause: element definition resolves to an object that has children but the element defines its own children. The children cannot be merged

Action: Remove the child elements from the definition
Level: 1

Type: ERROR

Impact: Programmatic

RCS-03054: end of EL expresssion not found [{0}]

Cause: while parsing an EL expression, the end of the expression could not be found

Action: remove or correct the expression
Level: 1

Type: WARNING

Impact: Logging

RCS-04000: error while processing predicate [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-04001: query expression [{0}] is invalid

Cause: The query string does not conform to the JNDI query syntax (RFC 2254)

Action: Use a query string that conforms to the JNDI query syntax (RFC 2254)
Level: 1

Type: ERROR

Impact: Programmatic

RCS-04002: query expression [{0}] contains invalid wildcard syntax

Cause: Wildcards can only be used with the EQUALS operator

Action: Modify the query expression so wildcards are only used with the EQUALS operator
Level: 1

Type: ERROR

Impact: Programmatic

RCS-04003: The type [{1}] of attribute [{0}] does not implement the Comparable interface.

Cause: The specified attribute value is of an unsupported data type that does not implement the Comparable interface. All attributes declared as searchable by a resource catalog adapter schema must implement this interface.

Action: Modify the resource catalog schema for the source adapter so this attribute is not searchable or modify the attribute's datatype so it is Comparable.
Level: 1

Type: ERROR

Impact: Logging

RCS-04004: error while comparing catalog item [{0}] with [{1}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-04010: An error has occurred while searching folder [{1}] in catalog [{0}]. The folder was skipped. Implementation class=[{2}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-04011: An error has occurred while searching folder [{1}] in repository [{0}]. The folder was skipped. Implementation class=[{2}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-04012: An error has occurred while searching custom folder [{1}] in catalog [{0}]. The folder was skipped. Implementation class=[{2}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-04013: attribute [{0}], value [{1}], has an unsupported data type [{2}]

Cause: An attribute returned a value with an unsupported data type. The value was converted to a String.

Action: Ensure that the values for all resource catalog attributes correspond to one of the supported data types defined by oracle.adf.rc.attribute.AttributeConstants
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-05000: error processing transfer set [{0}]

Cause: An exception was raised by an underlying component.

Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-05002: transfer set [{0}] is empty

Cause: The transfer set did not include any connection or catalog entries.

Action: Create a transfer set containing at least one connection or one catalog and then repeat the operation.
Level: 1

Type: ERROR

Impact: Logging

RCS-05003: An error has occurred while transferring connections in transfer set [{0}]. The failure control is set to [{1}].

Cause: An exception was raised by an underlying component and the transfer process was configured to fail when encountering an error.

Action: Review the cause of the failure, correct it, and then restart the transfer process. Alternatively, change the failure controls to ignore errors.
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-05004: An error has occurred transferring connection [{1}] in transfer set [{0}]. The failure control is set to [{2}].

Cause: An exception was raised by an underlying component and the transfer process was configured to fail when encountering an error.

Action: Review the cause of the failure, correct it, and then restart the transfer process. Alternatively, change the failure controls to ignore errors.
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-05005: Connection ID [{1}] in transfer set [{0}] already exists in the target environment. The duplicates control is set to [{2}].

Cause: A connection included in the specified transfer set already exists in the target environment and the duplicates control is set to fail upon detecting a duplicate.

Action: Remove the duplicate connection from the target environment and then restart the transfer process. Alternatively, change the duplicates control to overwrite or ignore duplicates.
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-05006: An error has occurred while transferring catalogs in transfer set [{0}]. The failure control is set to [{1}].

Cause: An exception was raised by an underlying component and the transfer process was configured to fail when encountering an error.

Action: Review the cause of the failure, correct it, and then restart the transfer process. Alternatively, change the failure controls to ignore errors.
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-05007: An error has occurred while transferring catalog [{1}] in transfer set [{0}]. The failure control is set to [{2}].

Cause: An exception was raised by an underlying component and the transfer process was configured to fail when encountering an error.

Action: Review the cause of the failure, correct it, and then restart the transfer process. Alternatively, change the failure controls to ignore errors.
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-05008: Catalog ID [{1}] in transfer set [{0}] already exists in the target environment. The duplicates control is set to [{2}].

Cause: A catalog included in the specified transfer set already exists in the target environment and the duplicates control is set to fail upon detecting a duplicate.

Action: Remove the duplicate catalog from the target environment and then restart the transfer process. Alternatively, change the duplicates control to overwrite or ignore duplicates.
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-06001: An unexpected error has occurred destroying a pooled object. Pool=[{0}]

Cause: Review the root cause of the exception for more details.

Action: If the root cause does not provide sufficient information to resolve the issue, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-06002: leakage detected while destroying object pool [{0}]. In-use count=[{1}]

Cause: An attempt was made to destroy an object pool when objects were still in use. This is a potential memory leak

Action: Identify the clients of the object pool and ensure all objects are returned to the pool before it is destroyed.
Level: 1

Type: WARNING

Impact: Programmatic

RCS-23000: An unexpected error has occurred.

Cause: Review the root cause of the exception in the log file for more details.

Action: If the root cause does not provide sufficient information to resolve the issue, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

13 TPC-00001 to TPC-90049

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 or you do not have access to it.

Cause: No item with the specified ID exists or user does not have access to view it.

Action: Enter another valid ID value.
Level: 1

Type: ERROR

Impact: Logging

TPC-00018: Specify your 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 descendant 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 which should be in email format, abc@xyz.net.
Level: 1

Type: ERROR

Impact: Logging

TPC-00062: Failed to connect to chat server "{0}".

Cause: The connection information is incorrect.

Action: Verify the connection information.
Level: 1

Type: ERROR

Impact: Logging

TPC-00063: Failed to log in to chat server "{0}".

Cause: The login credentials are incorrect.

Action: Verify the login credentials and connection information.
Level: 1

Type: ERROR

Impact: Logging

TPC-00064: Failed to save the work item.

Cause: Some of the workitem field values are invalid.

Action: Verify the input data.
Level: 1

Type: ERROR

Impact: Logging

TPC-00065: Failed to update password.

Cause: The password is invalid.

Action: Ensure the password is 12 characters or less.
Level: 1

Type: ERROR

Impact: Session

TPC-00066: Failed to log in to team server.

Cause: The login credentials are incorrect.

Action: Verify the login credentials.
Level: 1

Type: ERROR

Impact: Session

TPC-00067: Invalid username 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 in this format, abc@xyz.net.
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-00122: Password for "{0}" is not valid after the login was renamed. Make sure you reset the password.

Cause: The user's login was renamed. Its password is no longer valid

Action: Reset the password for the login.
Level: 1

Type: WARNING

Impact: Logging

TPC-00123: Repository name cannot contain any of these characters: #/\?

Cause: The repository name contains invalid character(s)

Action: Provide valid repository name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00124: Please provide value for first name, last name, or email.

Cause: Value for first name,last name, or email is not specified.

Action: Provide valid value.
Level: 1

Type: ERROR

Impact: Logging

TPC-00125: Cannot save the user profile.

Cause: The user information specified cannot be saved.

Action: Provide valid user profile values and try it again.
Level: 1

Type: ERROR

Impact: Logging

TPC-00126: Query name cannot be empty. Please provide a valid name.

Cause: The query name is blank.

Action: Provide valid query name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00127: The new query name cannot be the same as the original name.

Cause: The new query name is the same as the original name.

Action: Provide a new query name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00128: Query name cannot contain any of these characters: #/\?

Cause: The query name contains invalid character(s)

Action: Provide valid query name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00129: The specified query name already exists. Please provide a different name.

Cause: An existing query with the name specified already exists.

Action: Provide a different query name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00130: Input will be used in url and cannot contain #, ? / or \.

Cause: Input text contains #, ?, / or \.

Action: Remove #, ?, / or \.
Level: 1

Type: ERROR

Impact: Logging

TPC-00131: Failed to save to Preferences.

Cause: TPC unabled to save to JDeveloper Preferences.

Action: Try again later.
Level: 1

Type: ERROR

Impact: Logging

TPC-00132: Cannot activate a team whose parent team "{0}" is inactive. Activate the parent team then this team.

Cause: Activating a team whose parent is inactive is not allowed.

Action: Activate the parent team before activating the team.
Level: 1

Type: ERROR

Impact: Logging

TPC-00133: Default email client is not configured. Configure a default email client.

Cause: Default email client is not configured.

Action: Configure a default email client.
Level: 1

Type: ERROR

Impact: Logging

TPC-00134: Chat server does not support offline messages. Please try IM later or sending an Email.

Cause: Chat server does not support offline messages.

Action: Try IM later or sending an Email.
Level: 1

Type: ERROR

Impact: Logging

TPC-00135: Your client version "{0}" is currently not compatible with TPC server version "{1}". Download a patch to fix this problem.

Cause: You need to install a TPC patch to fix this issue.

Action: Contact Oracle Support if the patch is not available.
Level: 1

Type: ERROR

Impact: Logging

TPC-00136: Build and test data is not available.

Cause: Test integration web service is down or JDeveloper used is not compatible with the test web servcice.

Action: Contact your Team Productivity Center administrator to get it resolved.
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-60018: Cannot create a null record.

Cause: You try to create a null record.

Action: Make sure the record has valid contents.
Level: 1

Type: ERROR

Impact: Threads

TPC-60019: The branch or label series "{0}" has already existed.

Cause: You try to create a branch or label series that has already existed.

Action: Check the name of your branch or label series. It must be unique per SCM connector.
Level: 1

Type: ERROR

Impact: Threads

TPC-60020: The branch "{0}" does not exist.

Cause: The branch you want to update does not exist.

Action: Specify a valid branch.
Level: 1

Type: ERROR

Impact: Threads

TPC-60021: The branch "{0}" you want to create or update is for a non-existing SCM connector "{1}".

Cause: The branch references the non-existing connector.

Action: Specify a valid SCM connector.
Level: 1

Type: ERROR

Impact: Threads

TPC-60022: The branch "{0}" you want to create or update is for a non-existing team "{1}".

Cause: The branch references the non-existing team.

Action: Specify a valid team.
Level: 1

Type: ERROR

Impact: Threads

TPC-60023: You must specify an SCM connector name for querying the branch "{0}".

Cause: The branch query requires an SCM connector name.

Action: Specify an SCM connector.
Level: 1

Type: ERROR

Impact: Threads

TPC-60024: You must specify a branch name for querying the build dashboard "{0}".

Cause: You did not specify a branch name used to query the specified build dashboard.

Action: Provide branch name.
Level: 1

Type: ERROR

Impact: Threads

TPC-60025: Build dashboard "{0}" for branch "{1}" does not exist.

Cause: There is no record for specified build and branch.

Action: Verify that you sepcified correct information.
Level: 1

Type: ERROR

Impact: Threads

TPC-60026: Dashboard for build "{0}" has already existed.

Cause: You try to create a build dashboard that has already existed.

Action: Check the name of your build.
Level: 1

Type: ERROR

Impact: Threads

TPC-60027: Missing branch or connector for creating the build dashboard "{0}".

Cause: You need to specify the branch and SCM connector when creating a build dashboard.

Action: Check the name of your build.
Level: 1

Type: ERROR

Impact: Threads

TPC-60028: The build dashboard "{0}" does not exist.

Cause: The build dashboard you want to update does not exist.

Action: Specify a valid build dashboard.
Level: 1

Type: ERROR

Impact: Threads

TPC-60029: This operation is not supported.

Cause: The requested operation is not supported.

Action: Try some other time.
Level: 1

Type: ERROR

Impact: Threads

TPC-60030: "{0}" with parent ID "{1}" will not be created as it is missing required Dashboard ID.

Cause: You need to specify the build dashboard id when creating a build summary for it.

Action: Specify the build id.
Level: 1

Type: WARNING

Impact: Threads

TPC-60031: {0} "{1}" for build "{2}" has already existed.

Cause: You try to create a build summary that has already existed.

Action: Check the name of the build summary.
Level: 1

Type: ERROR

Impact: Threads

TPC-60032: Changeset "{0}" for "{0}" has already existed.

Cause: You try to create a build changeset that has already existed.

Action: Check the name of the build changeset.
Level: 1

Type: ERROR

Impact: Threads

TPC-60033: You must specify an SCM connector name and a product/release name for this query.

Cause: This branch query requires both an SCM connector name and a product/release name.

Action: Specify both information
Level: 1

Type: ERROR

Impact: Threads

TPC-60034: Repository "{0}" has already existed.

Cause: You try to create a repository that has already existed.

Action: Check the name of your repository.
Level: 1

Type: ERROR

Impact: Threads

TPC-60035: The repository "{0}" does not exist.

Cause: The repository you want to update does not exist.

Action: Specify a valid repository.
Level: 1

Type: ERROR

Impact: Threads

TPC-60036: Missing test result Id for creating workitem "{0}" using repository "{0}".

Cause: You need to specify the test result Id when creating a workitem for it.

Action: Specify the test result Id.
Level: 1

Type: ERROR

Impact: Threads

TPC-60037: The workitem key and repository for test result Id "{0}" are missing.

Cause: You asked to create a workitem for a test result but you did not specify a key and repository for the workitem.

Action: Specify the key and repository.
Level: 1

Type: ERROR

Impact: Threads

TPC-60038: The test result "{0}" does not exist.

Cause: The test result you want to update does not exist.

Action: Specify a valid test result.
Level: 1

Type: ERROR

Impact: Threads

TPC-60039: Workitem "{0}" specified for test result Id "{0}" has already existed.

Cause: You try to create a workitem for a test result but the workitem has already existed.

Action: Specify a valid workitem.
Level: 1

Type: ERROR

Impact: Threads

TPC-60040: Workitem "{0}" has already existed in the repository "{0}".

Cause: You try to create a workitem that has already existed.

Action: Check the key and repository used for the workitem are correct.
Level: 1

Type: ERROR

Impact: Threads

TPC-60041: TPC server version "{0}" is not valid. Expected at least in this format: #.#.#.#

Cause: This is an internal error caused by invalid server version recorded on the database.

Action: Contact TPC Administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-60042: TPC client version "{0}" is not valid. Expected at least in this format: #.#.#.#

Cause: This is an internal error caused by invalid client version.

Action: Correct your TPC client installation. You can do this by removing the old one then reinstall, or install correct TPC client to another JDeveloper client.
Level: 1

Type: ERROR

Impact: Logging

TPC-60043: Your client version "{0}" is newer than your TPC server version "{1}". 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 your TPC server version "{1}". Download a patch to fix this problem.

Cause: You need to install a TPC patch to fix this issue.

Action: Contact Oracle Support if the patch is not available.
Level: 1

Type: ERROR

Impact: Logging

TPC-60045: Cannot find owner "{0}" to remove from build summary "{1}".

Cause: You ask to remove owner which does not exist for the specified build summary.

Action: Specify correct build summary.
Level: 1

Type: ERROR

Impact: Logging

TPC-60046: Cannot establish connection to TPC repositories.

Cause: TPC server cannot connect to the database.

Action: Check if you specified username and password to connect to the database correctly.
Level: 1

Type: ERROR

Impact: Logging

TPC-60047: Created By is required to create the task but is missing. It should be set to current logged-in user.

Cause: This is an internal error caused by missing Created By in the input specified by the caller.

Action: Contact Oracle Support
Level: 1

Type: ERROR

Impact: Logging

TPC-60048: The task "{0}" with Id "{1}" does not exist.

Cause: The task you want to update does not exist.

Action: Specify a valid task.
Level: 1

Type: ERROR

Impact: Threads

TPC-60049: The task "{0}" for team "{1}" does not exist.

Cause: The task you want to delete or retrieve does not exist.

Action: Specify a valid task.
Level: 1

Type: ERROR

Impact: Threads

TPC-60050: The task Id to retrive, delete, or update is null.

Cause: Missing task Id.

Action: Specify a valid task Id.
Level: 1

Type: ERROR

Impact: Threads

TPC-60051: Team Id cannot be null.

Cause: Missing team Id.

Action: Specify a valid team Id for the task you want to retrieve.
Level: 1

Type: ERROR

Impact: Threads

TPC-60052: Task name you want to retrive is null.

Cause: Missing task name.

Action: Specify a valid task name.
Level: 1

Type: ERROR

Impact: Threads

TPC-60053: Task you want to delete is missing from input.

Cause: Task to delete is missing from input.

Action: Specify a valid task.
Level: 1

Type: ERROR

Impact: Threads

TPC-60054: Multiple tasks were found with the name "{0}".

Cause: The API expects to return one task only but multiple tasks were found.

Action: Use other APIs.
Level: 1

Type: ERROR

Impact: Threads

TPC-60055: Assigned To Id "{0}" does not exist.

Cause: Assigned To Id cannot be found

Action: Specify correct Assigned To Id
Level: 1

Type: ERROR

Impact: Threads

TPC-60056: Cannot find user associated with login "{0}".

Cause: Cannot find user associated with the specified login

Action: Specify correct login
Level: 1

Type: ERROR

Impact: Threads

TPC-60057: Assigned To Id cannot be null.

Cause: Assigned To Id is null

Action: Specify correct Assigned To Id
Level: 1

Type: ERROR

Impact: Threads

TPC-60058: JPA Query string to execute is empty.

Cause: Internal error

Action: Contact Oracle Support
Level: 1

Type: ERROR

Impact: Threads

TPC-60059: Cannot retrieve values for null lookup type.

Cause: Internal error

Action: Contact Oracle Support
Level: 1

Type: ERROR

Impact: Threads

TPC-60060: Query name "{0}" already exists. Please refresh workitem panel and use another name.

Cause: Query name already exists

Action: Use another name
Level: 1

Type: ERROR

Impact: Threads

TPC-60061: Cannot find user credential to access TPC database.

Cause: User credential to connect to TPC database cannot be found.

Action: Reinstall TPC Server.
Level: 1

Type: ERROR

Impact: Process

TPC-60062: Cannot find persistence.xml.

Cause: Cannot find persistence.xml for acessing database.

Action: Reinstall TPC Server.
Level: 1

Type: ERROR

Impact: Process

TPC-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 update "{0}" file. Make sure the destination folder is not read only.

Cause: Cannot update the specified 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 application server directory "{0}" for "{1}" deployment 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 "{0}" shipped in the installer jar is invalid. The installer image may be corrupted. Download a working copy of the installer.

Cause: The specified war file is invalid or corrupted.

Action: The installer 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 one or more componets 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 "{1}" already exists and cannot be overwritten. Make sure it has write permission.

Cause: The specified file already exists and cannot be overwritten.

Action: Make sure the specified file has write permission.
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 "{1}".

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

TPC-90023: This installer should upgrade database schema with prefixed between "{0}" or "{1}";. It cannot apply to current installed version "{2}".

Cause: The current version is not an immediate precedent version for the installer to upgrade from.

Action: Upgrade sequentically from the current version.
Level: 1

Type: ERROR

Impact: Logging

TPC-90024: Installer does not know how to parse this SQL statement: "{0}".

Cause: The sql statement is not in the parsing range of the installer.

Action: Report the problem to include the sql parsing for this statement in the installer.
Level: 1

Type: ERROR

Impact: Logging

TPC-90025: Installer cannot install connector only. Please go back to choose server installation.

Cause: User chose connector only for new installation.

Action: Go back to choose server installation.
Level: 1

Type: ERROR

Impact: Logging

TPC-90026: The otpc.war of current installation for upgrade is missing in the server deployment directory.

Cause: The otpc.war for current installation cannot be found.

Action: Make sure the directory name is correct and the otpc.war of current installation is there.
Level: 1

Type: ERROR

Impact: Logging

TPC-90027: Failed to deploy Test Plugin for CruiseControl.

Cause: Failed to deploy Test Plugin for CruiseControl.

Action: Make sure the specified deployment directory is correct and the tpc-test-collector.jar of current installation is there.
Level: 1

Type: ERROR

Impact: Logging

TPC-90028: Failed to create test.properties.

Cause: Failed to create test.properties.

Action: Make sure the directory name is correct.
Level: 1

Type: ERROR

Impact: Logging

TPC-90029: Failed to generate keystore file.

Cause: Failed to generate keystore file.

Action: Contact Oracle technical support
Level: 1

Type: ERROR

Impact: Logging

TPC-90030: There is a schema already created in database.

Cause: Try to perform new installation on a database instance where there exists a schema.

Action: Perform schema upgrade or clean current schema.
Level: 1

Type: ERROR

Impact: Logging

TPC-90031: There is no schema in the database to upgrade from.

Cause: Try to perform upgrade operation on a database instance without prior installation.

Action: Perform new installation.
Level: 1

Type: ERROR

Impact: Logging

TPC-90032: No installation type selected for new or upgrade operation.

Cause: No installation type selected for new or upgrade operation.

Action: Select new or upgrade installation.
Level: 1

Type: ERROR

Impact: Logging

TPC-90033: None of server name, port, admin login or admin password should be null.

Cause: One or more fields of server name, port, admin login or admin password is null.

Action: Enter values for server name, port, admin login and admin password.
Level: 1

Type: ERROR

Impact: Logging

TPC-90034: Please make sure the fields are not empty and verify your password.

Cause: Admin login or admin password is null.

Action: Enter values for admin login and admin password.
Level: 1

Type: ERROR

Impact: Logging

TPC-90035: Empty value. Please enter the directory for {0}.

Cause: No value entered for directory.

Action: Enter values for directory.
Level: 1

Type: ERROR

Impact: Logging

TPC-90036: {0} is not a valid directory. Please correct it.

Cause: Input value is not a valid directory.

Action: Correct directory value.
Level: 1

Type: ERROR

Impact: Logging

TPC-90037: Failed to deploy Hudson server.

Cause: Failed to deploy Hudson server.

Action: Check permission and space for its deployment directory.
Level: 1

Type: ERROR

Impact: Logging

TPC-90038: Failed to install CruiseControl Plugin

Cause: Installer encountered error during installing CruiseControl Plugin

Action: Check the log file for permission and space problem in the deployment directory.
Level: 1

Type: ERROR

Impact: Logging

TPC-90039: Cannot copy "{0}" to "{1}". Make sure the directory 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-90040: File "{0}" either does not exist or cannot be read.

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-90041: Failed to install Hudson Plugin

Cause: Installer encountered error during installing Hudson Plugin

Action: Check the log file for permission and space problem in the deployment directory.
Level: 1

Type: ERROR

Impact: Logging

TPC-90042: Failed to deploy Test Plugin for Hudson.

Cause: Failed to deploy Test Plugin for Hudson.

Action: Make sure the specified deployment directory is correct.
Level: 1

Type: ERROR

Impact: Logging

TPC-90043: No type is selected for application server.

Cause: No selection for application server type.

Action: Select application server type.
Level: 1

Type: ERROR

Impact: Logging

TPC-90044: The input value is not a valid port number.

Cause: The input value is not a valid port number.

Action: Enter valid port number for the input field.
Level: 1

Type: ERROR

Impact: Logging

TPC-90045: Server address contains character(s) other than letters, digits, hyphens and dots.

Cause: Server address contains character other than letter, digit and dot.

Action: Correct invalid characters.
Level: 1

Type: ERROR

Impact: Logging

TPC-90046: No plugin has been selected. Select one or more plugins to install.

Cause: No plugin has been selected.

Action: Select the plugins to install.
Level: 1

Type: ERROR

Impact: Logging

TPC-90047: "{0}" is not a valid connector bundle file. Skip installation.

Cause: Invalid connector bundle file.

Action: Change to install from valid connector bundle file.
Level: 1

Type: ERROR

Impact: Logging

TPC-90048: Password must be at least 8 characters with at least 1 non-alphabetic character.

Cause: Either password is less than 8 characters or has all alphabetic characters.

Action: Change password to be at least 8 characters with at least 1 non-alphabetic character.
Level: 1

Type: ERROR

Impact: Logging

TPC-90049: Confirm password is not the same as the password.

Cause: Retyped password is not the same as the first one.

Action: Type the same password as the first one.
Level: 1

Type: ERROR

Impact: Logging

14 TPCTEST-00001 to TPCTEST-00001

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

15 UIX-00001 to UIX-00025

UIX-00001: The servlet is not getting initialized.

Cause: Servlet did not get initialized due to runtime errors

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact:

UIX-00002: names contain '$'

Cause: Tried to create a oracle.cabo.servlet.Page Object with its name containing a '$' character

Action: Remove the '$' character.
Level: 1

Type: ERROR

Impact:

UIX-00003: PageBroker entry is not present in the web.xml file.

Cause: The parameter (param-name=oracle.cabo.servlet.pageBroker) was missing in the web.xml file.

Action: Contact Oracle Support Services
Level: 16

Type: INCIDENT_ERROR

Impact:

UIX-00013: could not find renderer for {0}

Cause: A custom renderer Java class was not found.

Action: Check for ClassNotFoundException and other errors.
Level: 3

Type: ERROR

Impact:

UIX-00014: PageBroker was already initialized

Cause: Double initialization of the page broker or the UIX servlet.

Action: Check the code for the second initialization.
Level: 2

Type: ERROR

Impact:

UIX-00015: Could not create page flow engine: {0}

Cause: The following pageflow engine class could not be loaded: oracle.cabo.servlet.event.TrivialPageFlowEngine

Action: Contact Oracle Support Services
Level: 2

Type: INCIDENT_ERROR

Impact:

UIX-00016: File upload manager was not created: {0}

Cause: Could not load the custom FileUploadManager class or the default one given below. oracle.cabo.servlet.io.FileUploadManager

Action: Make sure the custom FileUploadManager is in classpath or the default one is as given below oracle.cabo.servlet.io.FileUploadManager
Level: 4

Type: ERROR

Impact:

UIX-00017: Listener was not created: {0}

Cause: Could not load one of the UIX listener classes or the default one given below. oracle.cabo.servlet.UIXRequestListeners

Action: Ensure all the custom listener clasees are in classpath or the default one is as given below oracle.cabo.servlet.UIXRequestListeners
Level: 4

Type: ERROR

Impact:

UIX-00018: The return type was invalid

Cause: The event handler method that was bound to an event in the UIX page had the incorrect return type.

Action: The return type of a event handler method is oracle.cabo.servlet.event.EventResult.
Level: 10

Type: ERROR

Impact:

UIX-00019: Method {0} was not static.

Cause: The event handler method that was bound to an event was not static.

Action: Ensure that the event handler method bound to an event is static.
Level: 10

Type: ERROR

Impact:

UIX-00020: The file was too large. The maximum file Size is: {0}

Cause: The multiple-part file is too large.

Action: Upload a smaller file.
Level: 28

Type: ERROR

Impact:

UIX-00021: Wildcarded events with explicit sources not supported for {0}

Cause: Event registration is not specific.

Action: Register a specific event.
Level: 10

Type: ERROR

Impact:

UIX-00022: The target was not a MutableDataObject {0}.

Cause: The class name provided was not a subclass of oracle.cabo.ui.data.MutableDataObject

Action: Programmatic error correction needed.
Level: 10

Type: ERROR

Impact:

UIX-00023: Target is not a MutableDataObject: {0}

Cause: One of the following servlet init parameter is not a number. oracle.cabo.servlet.io.MaxMemory oracle.cabo.servlet.io.MaxDiskSpace

Action: The following servlet init parameters should be numbers oracle.cabo.servlet.io.MaxMemory oracle.cabo.servlet.io.MaxDiskSpace
Level: 10

Type: ERROR

Impact:

UIX-00024: ActionEventHandler: cannot forward

Cause: The value obtained is not a valid server resource.

Action: Make sure that the forward value is a valid server resource.
Level: 28

Type: ERROR

Impact:

UIX-00025: QueueStateManager is expired

Cause:

Action: Contact Oracle Support Services
Level: 10

Type: INCIDENT_ERROR

Impact:

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